GitHub’s package firewall can screen npm installs made by coding agents
Added to DistroCool on 2026-10-21 · Discovery date, not a release announcement
GitHub’s package firewall entered public preview on October 20. It proxies metadata requests and package downloads from endpoints such as Actions runners and coding agents, then applies enterprise policies including a cooldown period, Advisory Database checks, and supply-chain checks such as attestation downgrades.
Why it matters
AI coding agents install dependencies quickly and autonomously, making package-install time a high-risk point for credential theft and supply-chain attacks. A policy layer between the agent and the public registry adds a useful control without relying on the agent to notice malicious packages. Today it is limited to npm and GitHub Enterprise Cloud; the preview is free, with metered billing planned at general availability.
Try this next.
For a disposable npm-based CI or coding-agent workload, have an enterprise administrator configure the firewall policy, route the endpoint through it, and attempt a normal dependency install. Confirm allowed packages resolve, blocked packages surface an exception workflow, and direct registry access is not still available. DistroCool has not independently tested this example.
Open the practical workflow →Source: GitHub Changelog — October 20, 2026 ↗