Radarr/Prowlarr

[westlandnigel]

Output of brew config

brew config
HOMEBREW_VERSION: 4.6.11
ORIGIN: https://github.com/Homebrew/brew
HEAD: 6c44d1a8f1bd7ca44c3f13c4e3694cdff40483a2
Last commit: 33 hours ago
Branch: stable
Core tap JSON: 16 Sep 04:35 UTC
Core cask tap JSON: 16 Sep 04:35 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_FORBID_PACKAGES_FROM_PATHS: set
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 3.4.5 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.4.5/bin/ruby
CPU: deca-core 64-bit arm_donan
Clang: 17.0.0 build 1700
Git: 2.50.1 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 26.0-arm64
CLT: 26.0.0.0.1.1757719676
Xcode: N/A
Rosetta 2: false

Output of brew doctor

brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed casks are deprecated or disabled.
You should find replacements for the following casks:
  prowlarr
  radarr

Description of issue

Hello,

I don't know where to say it, but two of my casks will be disabled because it fails gatekeeping. This because after installing radarr: codesign --force --deep -s - /Applications/Radarr.app && xattr -rd com.apple.quarantine /Applications/Radarr.app You have to do this which says on macos part on radarr.video and for prowlarr (prowlarr.com) codesign --force --deep -s - /Applications/Prowlarr.app && xattr -rd com.apple.quarantine /Applications/Prowlarr.app which also says it on site. Can't this just be implemented in the cask so that it doesn't have to be disabled?

Relevant casks

radarr, prowlarr

[bevanjkay]

This is not something that we should be doing automatically for users, as it works around a valuable security feature in macOS. You could consider hosting the casks in your own tap if you would like to use Homebrew to manage them after they are disabled, or alternatively ask the developers to consider codesigning the applications.

[p-linnane]

No, we do not intentionally bypass macOS security mechanisms. If the applications won't be notarized, they will be deprecated and removed. You can consider hosting them in your own Tap if you'd like.