INSTALL MOCKINGBYRD
Two ways in, the same build either way. Apple silicon, macOS 14 or later. The disk image is signed with a Developer ID and notarized, so it opens on a double-click without a Gatekeeper warning.
-
Download
One disk image, either way you install.
-
Open
No sign-in. Nothing to sign up for, and what it measures stays on your device. The trial runs seven days.
-
Read your score
Scored on open. Nothing changes until you read a fix and apply it.
Most people want this
Download the disk image
Double-click it, drag Mockingbyrd into Applications, and open it. macOS checks the signature on first launch and lets it through without a warning.
Check what you downloaded
Every build is published with its checksum. Homebrew verifies this for you; if you took the disk image by hand and want to check it yourself:
shasum -a 256 ~/Downloads/Mockingbyrd.dmg
It should print:
the value published in the manifest
If you already use Homebrew
Install with Homebrew
The tap keeps Mockingbyrd alongside everything else you install, and upgrades it with the same command you use for the rest.
brew tap mockingbyrd-io/mockingbyrd
brew trust --cask mockingbyrd-io/mockingbyrd/mockingbyrd
brew install --cask mockingbyrd
The middle line is the tap-trust step: Homebrew refuses to load a cask from a third-party
tap until you say so. If your Homebrew is older than that step, the line prints
Error: Unknown command: trust and nothing else happens — run the first
and third lines and carry on. Any other message is a real failure and worth reading; this
is the only one to expect here.
Afterwards brew upgrade --cask mockingbyrd moves you to the next release, and
for a copy installed this way it is the only route: the app checks whether a newer build
exists, and when Homebrew put it there it says so and hands you that command rather than
replacing a bundle brew still has a receipt for.
Installed from the disk image instead, the app can fetch and install a release itself. It does not do so unasked — “Install updates without asking” in Settings starts off, and until you turn it on a new build is a button you press. Either way the same three things have to hold before anything is replaced: the download matches the checksum published beside it, it carries a Developer ID signature from the team that signs Mockingbyrd, and Apple has notarized that exact image. Any one of them missing and the build is refused, with the reason in the Monitor.
If you tapped marco-buhlmann/mockingbyrd before the move, it still works —
GitHub redirects the old address. To have it named after the organization:
brew untap marco-buhlmann/mockingbyrd, then the tap line above. Untapping
does not remove an installed app.
To remove it: brew uninstall --cask mockingbyrd, or
brew uninstall --zap --cask mockingbyrd to take its settings too.
Remove the guard first, if you installed it. It is a
PreToolUse entry in your agent’s own settings file, which Homebrew does not
own and neither uninstall touches — so left alone it keeps inspecting calls after the
app is gone. Use Enforcement → Remove in the app, or run
_guard-uninstall.sh from the fixes folder. Either one unregisters the hook and
moves the script aside rather than deleting it.