Homebrew to Remove --no-quarantine Flag Support for macOS Security Compliance
By
firexcy
6mo ago· 2 min readenCode
65/100
Toasty
Bagelometer↗
Lightly browned and well buttered. A solid pick from the rack.
Score65TypenewsSentimentneutral
Summary
Homebrew is removing support for the `--no-quarantine` flag for casks, which bypasses macOS Gatekeeper security to run unsigned/unnotarized applications. This change is due to Apple's enhanced security measures in recent macOS versions, including stricter runtime protection and requirements for valid signatures on Apple silicon. Support for casks that fail Gatekeeper checks will end on September 1, 2026, as Apple continues to strengthen macOS security mechanisms.
Key quotes
· 4 pulled--no-quarantine is used to forcibly bypass Gatekeeper, which is a built-in macOS security mechanism
macOS Tahoe is the final release to support Intel systems, and last year Apple updated macOS runtime protection to make it harder to override Gatekeeper
Macs with Apple silicon also don't 'permit native arm64 code to execute unless a valid signature is attached'
we are ending support for all casks that fail Gatekeeper checks on September 1st, 2026
Verification This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose...
