GitHub Puts a Firewall Between npm and the Agents That Install Packages

Coding agents and CI runners install dependencies all day without a person watching, and that makes them an easy target for poisoned packages. GitHub’s answer is a package firewall that sits between those machines and the public npm registry, now in public preview for GitHub Enterprise Cloud customers.

The firewall inspects both metadata requests and package downloads and acts as what GitHub calls “an install-time policy gate.” Endpoints point at the firewall instead of going straight to upstream registries, and every request is checked against rules an administrator sets for the enterprise. GitHub announced the preview in a changelog post on Tuesday and rewrote the entry Wednesday “for clarity.”

The company tied the launch to “a recent flood of malware attacks that exploit systems at package installation time.” WebProNews reported last month on malicious npm packages that stole AWS keys and GitHub tokens, the kind of install-time attack this tool is built to stop.

What admins can set

The policy options at launch are a configurable cooldown period, checks against the GitHub Advisory Database for malware or vulnerability advisories, and supply-chain checks such as attestation downgrades.

GitHub said a user whose package is wrongly blocked can request an exception through a workflow similar to the one used in other GitHub Advanced Security features.

There are limits. The firewall supports only npm for now, so Python, Java and Go shops get nothing from it yet. It is open to GitHub Enterprise Cloud customers, including those using Enterprise Cloud with data residency. Setup steps are in GitHub’s documentation on protecting endpoints with package firewall.

The preview is free. GitHub said it will move to metered billing “similar to Actions billing” at general availability but has not published rates or a date for that switch.

Source: GitHub Changelog