GitHub has rolled out a preview of a package firewall that blocks suspicious npm packages while they are being installed. According to the company, the firewall inspects both metadata requests and package downloads for signs of malicious activity, acting as an install-time policy gate.
The feature currently covers only npm packages and is available in public preview to all GitHub Enterprise Cloud customers, including data-resident environments. The Microsoft-owned company positions the firewall between endpoints or internal registries and upstream package repositories, so requests route through it rather than hitting public registries directly.
That setup is meant to counter attacks that compromise systems when packages are installed, a risk that grows when AI agents and CI runners pull in dependencies automatically without explicit permission. Administrators set the policy controls: blocking known malware via the GitHub Advisory Database, blocking packages by vulnerability severity (defaulting to critical only, with high, medium or any severity options), blocking attestation downgrades when a requested version lacks an SLSA attestation, blocking newly added preinstall or postinstall scripts, and enforcing a cooldown period from 1 to 365 days, defaulting to one day and disabled at zero. Packages blocked in error can be flagged for exception requests approved by enterprise administrators and security managers.
The launch arrives as Rust 1.100, due November 12, 2026, prepares a configurable minimum publish age via the global-min-publish-age option in cargo/config.toml, defaulting to seven days when unset. Similar waiting periods have appeared across npm, Python, Visual Studio Code, Ruby, Bun, pnpm and Yarn over the past year. Socket noted the tradeoff: legitimate fixes wait too unless developers make an exception, and malicious code does not become harmless with age, since a release that escapes detection can outlast the cooldown. The value, Socket said, is buying researchers, maintainers and registries time to act before the next dependency update carries an attack further.
Source: The Hackers News