Homebrew 7.0.0, released on September 13, brings vulnerability checking into the package manager itself. Mac and Linux users can now run brew vulns without installing a separate tap or gem. The useful question is what the command actually examined: a report with no findings can still leave packages unchecked. The release also strengthens installation safeguards, while keeping the decision to trust downloaded software firmly with the user. [1]
Start with the packages the check can see
Homebrew calls its package definitions formulae. With no package names supplied, brew vulns checks installed formulae against known vulnerabilities in the OSV database. It is a version-and-advisory check, not a search through your files for malicious code. For an existing Homebrew installation, these commands update the package manager and run the check while exposing coverage gaps: [2]
brew update
brew vulns --list-skipped
The second command lists packages skipped because their source URL is missing or unsupported. Read that list alongside the findings. A skipped package has not received a clean bill of health; the tool lacked the information needed for that check. The documented scope is formulae, so do not read the result as an audit of every Mac application or every dependency inside a project.
For named formulae, --deps also checks their dependencies. The --fix-available filter shows findings with a released version fix; it does not install those fixes. Use the report to identify the affected package and review its update, rather than assuming the check repaired anything. Homebrew’s new advisory database also tracks the versions and revisions it ships, including backported security fixes. That matters when a distributor fixes a flaw without adopting the newest upstream version. [1]
A package definition can execute before the app opens
A tap is a repository of Homebrew package definitions and commands. Those definitions can contain Ruby code that Homebrew evaluates while loading them. Trust therefore starts before the familiar moment of launching an installed application. Homebrew has required explicit trust for non-official taps by default since version 6.0.0; that baseline is not new in version 7. [3]
The official trust guide recommends approving only the specific formula, cask or command you need. Trusting an entire tap accepts its current and future entries. You can inspect existing trusted entries with brew trust. Treat a request for broader trust as a decision about whose code may execute, not an installation error to silence.
The distinction also explains why package checks cannot replace an incident investigation. In the separate Keyv npm compromise, repository hooks created execution paths beyond an ordinary package install. That was a different ecosystem and attack; the transferable lesson is to identify when code runs, not just which version is listed.
The sandbox has an exit
Version 7 tightens isolated build and installation operations, including restrictions on access to the home directory. On Linux it adopts Landlock; kernels without that support continue without Linux sandboxing, with brew doctor reporting the missing protection. An installation completing successfully does not establish that isolation was available. [1]
On macOS, vendor .pkg installers and installer script: actions run outside the cask sandbox because they may need broad filesystem access, system services or administrator privileges. A program you subsequently launch also runs with its normal user permissions. Installation restrictions are therefore no promise that an untrusted application becomes safe. [4]
Homebrew 7 makes two useful questions easier to ask: which installed formulae have known problems, and which installation operations are constrained? Keep a third question separate—whose software are you choosing to run?
References
- Mike McQuaid. Homebrew 7.0.0. Homebrew, September 13, 2026.
- Homebrew. brew(1): vulns. Command manual, accessed September 15, 2026.
- Homebrew. Tap Trust. Documentation, accessed September 15, 2026.
- Homebrew. Cask Cookbook: artifact trust and sandboxing. Documentation, accessed September 15, 2026.
