GitHub package firewall vets npm installs before they reach CI
GitHub Enterprise Cloud can route npm installs in Actions and coding agents through a firewall that checks metadata and downloads against its advisory database before code runs.
GitHub launched a package firewall in public preview on 20 October, announced at GitHub Universe. It sits between endpoints, Actions runners and coding agents, and the upstream registry, inspecting both metadata requests and the package download itself for signs of malicious activity before the code reaches a build.
Admins set policy first: configurable cooldown periods, checks against the GitHub Advisory Database for malware and vulnerability alerts, and detection of attestation downgrades. Endpoints are then configured to route through the firewall instead of hitting npm directly, and maintainers can request an exception if a package is blocked by mistake. Coverage is npm-only for now. It’s available exclusively to GitHub Enterprise Cloud customers, including those on data residency, and it’s free during the preview; GitHub says general availability pricing will follow a metered model similar to Actions billing.
Why it matters: this is aimed directly at the hijacked-package and worm-style attacks that have shown up repeatedly this month, where a compromised maintainer account ships malware straight to a live version on npm. A firewall that blocks the install before it runs beats relying on a lockfile audit after the fact.
The caveat: npm only, and Enterprise Cloud only during preview, so most open source maintainers and solo developers on github.com get none of this yet.