GitHub Launches Package Firewall in Public Preview

What happened

Administrators first set policy controls for their enterprise: available controls include a configurable cooldown period, checking the GitHub Advisory Database for malware or vulnerability alerts, and supply-chain checks such as attestation downgrades. Endpoints like coding agents and CI/CD hosts are then configured to route requests through the firewall instead of pointing directly at upstream package registries; metadata requests for package lists and actual package downloads flow through the firewall and are evaluated against the policy. If a package is blocked erroneously, users can request an exception through the standard workflow used by other GitHub Advanced Security features.

The capability is available in public preview starting today for all GitHub Enterprise Cloud customers, including data-resident GitHub Enterprise Cloud. GitHub said the service is free during the preview period and will be charged on metered usage at general availability, similar to Actions billing. Currently the package firewall only supports npm packages.

Key facts

1. Where it sits: Between endpoints (Actions runners, AI coding agents) and upstream package registries, inspecting metadata requests and package downloads.
2. Policy controls: Configurable cooldown periods, Advisory Database malware/vulnerability alert checks, and supply-chain checks such as attestation downgrades.
3. Availability: In public preview now for GitHub Enterprise Cloud (including data-resident); free during preview, metered billing at GA.
4. Ecosystem support: Currently npm packages only.
5. False positives: Exceptions can be requested through the standard GitHub Advanced Security workflow.