GitHub package firewall enters public preview, screening npm traffic between coding agents, CI and the registry
More malware now harvests credentials at install time; GitHub adds a checkpoint between Actions runners, coding agents and upstream registries.
// Key points
- The firewall inspects both package metadata requests and downloads, in public preview for all GitHub Enterprise Cloud customers, including data residency.
- Admins can set a cooldown period, check the GitHub Advisory Database for malware or vulnerability alerts, and run supply-chain checks like attestation downgrades; erroneous blocks go through an exception request.
- Coding agents and CI hosts must be configured to route requests through the firewall instead of going straight to upstream registries.
- Free during preview, metered like Actions at general availability; only npm packages are supported for now.
Builder's takeCoding agents install dependencies on their own, inside environments that hold secrets, and that's the most overlooked gap. Even without GitHub Enterprise, I'd do two things now: set a cooldown so npm doesn't pull versions published a few hours ago, and never inject production credentials while an agent is installing packages.
// Background · from #Coding agents
Full timeline →- Oct 21 Cloudflare and VoidZero introduce tsrs, a Rust port of the TypeScript compiler up to 8x faster than TypeScript 7.0 with about 70% less memory
- Oct 20 Cloudflare cuts the average cost of its internal AI code review 68%, from $2.43 to $0.77
- Oct 20 GitHub opens a Copilot model policy REST API at enterprise, team, app and organization level, generally available