Install Gate, now with a census of coding-agent daemons on fintech laptops

The core idea of install-gate, holding versions that are only N days old, is close to a commodity now. Every major package manager has a native cooldown setting. Socket Firewall and Aikido Safe Chain apply one for free across npm and Python and are already marketed against coding-agent installs. Writing a PreToolUse hook for this is a documented weekend project. Small teams are unlikely to pay per seat for the blocking alone. What I could not find is the experience at the moment an agent hits the gate. No tool I found explains to the human, in one screen, why the agent wants a particular version and what changed between the old and new tarball: new or changed install scripts, newly added network calls or domains, newly obfuscated or minified files, new binaries. Nothing then turns that review into an approval that gets recorded and shared across the team's agent sessions. Socket and Xygeni flag risky behaviour in a package, and npm diff gives raw diffs, but none of these is built into the Claude Code or Codex approval flow. A second unclaimed piece is handling agents that try to get around a block with curl, direct tarball fetches or registry overrides, specifically at the hook layer. Socket only handles this at the network level. So a new entrant's best shot is the release diff card plus team approval memory, sold as a review workflow, with the age gate as a free feature underneath. Even then it is exposed: Socket could ship the same card in its MCP server or as a Claude Code plugin quite easily, and per-seat pricing looks hard to defend against free tools from well-funded vendors.

• Native package-manager cooldowns (npm min-release-age, pnpm minimumReleaseAge, yarn, bun, uv exclude-newer, pip 26.1+)

  All the major JS and Python package managers now have a built-in minimum release age setting. npm added it in 11.10, pip has relative durations from 26.1, and uv and pnpm have had it for longer. Turning it on takes one line of config, for free, and it applies to agent-run installs just as much as human ones. This covers the core blocking feature of install-gate.

• Socket Firewall (sfw)

  A free CLI and network proxy covering npm, yarn, pnpm, pip, uv and cargo. It blocks known-malicious packages, including transitive ones, and a Webflow case study describes it holding newly published packages for a cooldown window. Socket explicitly targets coding agents: it strips disallowed versions from registry metadata so agents can't get around the block. Socket raised $60M and also runs a hosted MCP server that can be added to Claude Code.

• Aikido Safe Chain

  An open-source wrapper for npm, yarn, pnpm, bun, pip, uv and others. By default it blocks packages less than 48 hours old, and the threshold can be changed. It is free, and it comes from a funded security vendor that also sells device protection.

• Version Sentinel (Claude Code plugin)

  Uses PreToolUse hooks to stop Claude Code from installing or editing manifests for npm, pip, cargo and dotnet until the version has been checked. It targets hallucinated versions rather than package age, but it already uses exactly the hook mechanism install-gate would.

• ShipWithAI Claude Code supply-chain hooks guide

  A published tutorial on writing PreToolUse hooks that match npm install commands and block them. It shows that building the hook is a do-it-yourself weekend project.

• set-minimum-package-release-age and dotfiles release-age modules

  Open-source scripts that set a 7-day cooldown across pip, uv, npm, pnpm, bun and yarn in one step. DJRHails' dotfiles has a similar module and describes it as the counterpart to sfw.

• package-verify-guard

  An open-source guard that checks packages before install. An open issue proposes adding a per-version age threshold, so it is moving toward the same feature.

• npm diff / libnpmdiff

  Built into npm. It fetches the registry tarballs for two versions and produces a unified diff, which is the raw material for the release diff card.

• Xygeni suspicious scripts detector

  A commercial detector that flags changes to npm install scripts between the current and previous version. That is one part of what the diff card would summarise.

Checked 2026-10-12