Mac Dev Toolchain Security
For people who install code for a living. The 10-minute checklist hardens the Mac — this covers what runs on top of it.
Pick one install guard
Three tools block malicious packages at install time. Same job, different coverage — don't run two.
- Aikido Endpoint Protection — free for 2 devices. Catches installs your IDE spawns too, not just ones you type. Recommended.
- Aikido SafeChain — free, no account. Shell wrappers for npm, yarn, pnpm, pip, uv, poetry. Blind spot: an install the IDE runs itself skips the wrapper.
- Socket Firewall —
npm i -g sfw, thensfw npm install. Nothing resident; you opt in per command.
git clone, or curl | sh.
Editor extensions
Extensions run arbitrary code with your permissions and auto-update silently. No extensible editor? Skip this section — there's no surface to audit.
- Run
code --list-extensionsand remove what you don't use. Nocode? Enable it via Command Palette → "Shell Command: Install 'code' command in PATH", or list the folder directly:ls ~/.vscode/extensions— Cursor uses~/.cursor/extensions, JetBrains add-ons live under~/Library/Application Support/JetBrains/. - Install only from the in-app Marketplace. Never a linked
.vsix. - Check: verified publisher, plausible install count, repo link that resolves.
- Cursor/VSCodium pull from Open VSX — thinner review, so check the publisher name twice.
Brew over .dmg
brew installgets signed bottles.brew install --caskfetches the vendor's binary from a URL declared in the cask.- Run
brew info --cask <name>before installing — the download URL should be the vendor's real domain. - A cask beats a
.dmgfrom a search ad — the ad's provenance is nothing. brew bundle dump— keep a Brewfile so a rebuild pulls the same sources.
CI runners
- Don't install the endpoint agent on runners — it's built for an interactive Mac.
- Use SafeChain's CI integration, or SocketDev/action — prefix install steps with
sfw. - Pin actions to a commit SHA. Tags move; a re-pushed tag is a supply-chain attack.
Five-minute audit
- If you run an extensible editor:
code --list-extensionsorls ~/.vscode/extensions— extensions are installed software. Skip if you don't. - List:
brew list --cask— forgotten casks still auto-update from their original CDN. - Check
npm config list—registrymust behttps://registry.npmjs.org/; anything else resolves your installs somewhere else. - Search
git config --global --list | grep -i url— aninsteadOfyou didn't add redirects clones through someone else's mirror.
The ceiling: disposable devboxes
Every tool above guards a machine that persists. The ceiling is structural: run the toolchain in a single-use box with nothing to steal. A bad install inside dies with the box — no keys, no sessions, no path to your network.
What it doesn't do: warn you. It only limits the damage. Credentials you bring inside (SSH agent, mounted repo, live tokens) are exposed while the box lives, and a dep that looked clean still ships if you push it. Hosted, it costs ~$5–20/mo plus remote latency.
- Hosted: a single-use VPS, GitHub Codespace, or gitpod you destroy per task.
- Local: a dev container or disposable VM (OrbStack, UTM) — snapshot the base, work inside, delete.
- The Mac still needs the checklist — for everything you never move off it: editor, browser, signing keys.
Won't stop
- IDE-spawned installs slip past shell wrappers — only the endpoint tunnel sees them.
- A malicious release newer than the 24-hour age gate installs fine. Guards cut typosquat and known-bad risk; they're not a guarantee.
- Self-updating apps pull binaries through their own channels — Gatekeeper is what stands there.
git clone && makeis unguarded end to end. Read install scripts before running them.