Skip to content- Sources: primary
- Summary: GitHub's package firewall sits between endpoints or internal registries and upstream npm and inspects metadata requests and downloads. Admins can block known malware, versions with vulnerabilities above a chosen severity, versions missing an SLSA attestation that earlier versions had, newly added install scripts, and versions younger than a 1 to 365 day cooldown. It is in public preview for GitHub Enterprise Cloud, and blocked packages can be released through an exception request.
- Why it matters: Coding agents and CI runners can be pointed at a policy gate instead of the public registry, which limits exposure to freshly hijacked packages.