GitHub Previews npm Firewall to Stop Suspicious Packages at Install Time

GitHub has announced a preview of a new package firewall that blocks suspicious npm packages while they are being installed. It is available to all GitHub Enterprise Cloud customers, including data-resident GitHub Enterprise Cloud, and currently supports only npm. GitHub describes it as an install-time policy gate that inspects both metadata requests and package downloads for signs of malicious activity.

The firewall sits between developer endpoints or internal registries and the public package repositories. Coding agents and CI/CD hosts send their requests through it instead of connecting directly to public registries. This matters because AI agents and CI runners often install dependencies automatically, without explicit permission. The firewall checks downloads against policies such as a minimum package age and malware advisories, and blocks anything that fails. Administrators set the policies. The cooldown period can range from 1 to 365 days, with a default of 1 day, and can be turned off by setting it to 0. If a package is blocked by mistake, users can request an exception, which enterprise administrators and security managers can approve.

The same idea is spreading elsewhere. Rust 1.100, scheduled for release on November 12, 2026, is set to add a configurable minimum publish age. This gives security scanners and maintainers time to flag malicious crate releases before people can install them. If unspecified, a seven-day waiting period applies by default.