GitHub's package firewall screens npm installs in public preview
Enterprise Cloud can put a firewall between coding agents or CI and npm. It checks metadata and downloads. The preview is free, and only npm is covered.
Official source (opens in a new tab)
GitHub's changelog for 20 October 2026 puts the package firewall in public preview. It sits between endpoints such as Actions runners or coding agents and the upstream registries. It inspects package metadata requests and downloads. GitHub says this is aimed at malware that harvests credentials at install time, before the package's own code runs.
Admins set the policy: a cooldown period, checks against the GitHub Advisory Database for malware or vulnerability alerts, and supply-chain checks such as attestation downgrades. Agents and CI have to be pointed at the firewall. A mistaken block can go through an exception request. The preview is open to GitHub Enterprise Cloud customers, including data-resident Enterprise Cloud. It is free during the preview. At general availability, GitHub says it will be metered like Actions. Only npm packages are supported.
Who it's for: an enterprise whose coding agents and CI install npm packages on machines that hold credentials.
Fits: Best for Vibe Coding. Copilot stays at rank 4. The firewall is a supply-chain control, not a stronger coding agent, so the verdict is unchanged.