GitHub package firewall
An install-time policy gate between developer or CI endpoints and npm registries, blocking malicious or risky packages.
Overview
GitHub released the package firewall in public preview on October 20, 2026 for GitHub Enterprise Cloud, including data-resident environments. It sits between endpoints or internal registries and upstream package repositories, inspecting metadata requests and downloads so coding agents and CI/CD hosts route installs through it. Administrators set enterprise policies such as a configurable cooldown period, checks against the GitHub Advisory Database for malware and vulnerabilities, and supply-chain checks like attestation downgrades; users can request exceptions for wrongly blocked packages. It currently supports npm only.
This is a sourced directory entry. Features and capabilities are reported in the linked sources; this entry does not document independent Aymorphic testing.
Key features
- Install-time gate for metadata requests and package downloads
- Configurable cooldown period for newly published versions
- Checks against GitHub Advisory Database malware and vulnerability advisories
- Attestation-downgrade detection and exception request workflow
- npm only during preview
Use cases
- Stopping malicious npm packages from reaching coding agents and CI runners
- Enforcing enterprise-wide dependency policy without per-repo setup
Pricing
Free during public preview; metered usage billing similar to Actions at general availability.
Pricing reflects the source record and may change. Confirm current terms with the provider.
Dates and sources
- Released
- 20 Oct 2026
- Record updated
- 29 Oct 2026
- Record last checked
- 29 Oct 2026