Every package, with its size and when it last ran
Homebrew is a section of the Developer tab. It lists the formulae and casks you asked for by name, each with what it is, its version, its size on disk with every version counted, and when Vitals last saw one of its programs run. Turn on Include dependencies to see the libraries other packages pulled in, each with what needs it.
Homebrew only ever grows. A formula tried once two years ago is still there with its dependencies, a database installed for one project still starts at every login, and every upgrade leaves the old version behind.
brew list names packages. It does not say which you use, how much space each takes or which service is running. Each of those is a different command.
Packages you installed and never ran
The last-run label comes from Vitals’ own usage history: Running now, Today, This week, This month, Over a month ago or Not seen running. A command that finishes within a second is seldom caught.
Not Seen Running lists the packages Vitals has never seen run, with the space they take together. Uninstall is offered for a package nothing else needs, and runs brew uninstall after you confirm. The rest say what needs them.
brew services, with Start, Stop and Restart
Each Homebrew service shows whether it is running, stopped or stopped with an error, whether it starts when you log in, and whether it was started with sudo and runs as root. Start, Stop and Restart run brew services. A service you stop stays stopped until you start it again, and its ports are in the Ports section.
Updates and cleanup
A package with a newer version shows the version installed and the new one, with Upgrade on each and Upgrade All for the lot. A running service restarts on the new version.
Can Be Freed is what Homebrew’s old versions and downloads take. Clean Up runs brew cleanup. Vitals changes nothing by itself: every button names the brew command it will run and waits for you.
Four cards at the top give the totals: what is installed and its size, what has not been seen running, how many updates are ready, and how much can be freed. An assistant connected over MCP can ask what is installed, what has an update and what has not been seen running.
How to use it
- 1
Open Homebrew
Go to the Developer tab and choose Homebrew. Vitals asks brew what is installed, which takes a second or two.
- 2
Check Not Seen Running
These are the packages Vitals has never seen run, with the space they take. Uninstall one after a confirmation.
- 3
Check the services
Each says whether it is running and whether it starts when you log in. Stop one you do not need.
- 4
Upgrade and clean up
Upgrade one package or all of them, then run Clean Up to remove old versions and downloads.
The details
- Where
- Developer tab → Homebrew
- Listed
- Formulae and casks, with dependencies behind a switch
- Per package
- Version, size on disk, update waiting, when it last ran
- Last-run labels
- Running now, Today, This week, This month, Over a month ago, Not seen running
- Services
- Start, Stop and Restart, through brew services
- Changes
- Each one a brew command, run after a confirmation
- In Terminal
- vitals homebrew
Questions
How does Vitals know when a package last ran?
From its own usage history. When a program that a package installed is running, Vitals notes it. A command that finishes within a second is seldom caught.
Does Vitals change anything by itself?
No. Upgrade, Uninstall, Clean Up and the service buttons each run a brew command, after a confirmation that says which one.
Can it uninstall a package that others need?
No. Uninstall is offered for a package nothing else needs. The rest say what needs them.
Does it show casks too?
Yes. Formulae and casks are both listed.
How much does a cleanup free?
Vitals asks Homebrew, which keeps the versions an upgrade replaced and the files it downloaded. The figure is under Can Be Freed.
The same feature on the app's own site: vitalsmac.com/features/homebrew