GitHub introduced its package firewall on October 20. It sits between npm registries and endpoints such as Actions runners or coding agents, evaluating both package metadata requests and actual downloads. Administrators can set a cooldown period for new packages and block versions with known malicious or vulnerable signals.
For AI-assisted development, this is an interesting shift from finding problems after installation to intercepting risky dependencies before installation. That matters because malicious package install scripts can run before a developer ever launches the application.
Do not mistake the preview for a free toggle in a personal repository. GitHub says it is currently limited to Enterprise Cloud, supports npm only, and is free during preview with metered pricing planned later. A small independent team should treat it as a product to evaluate, not a protection already switched on.
What to do: Read the eligibility and setup details; keep dependency pinning and existing security checks in place if your account lacks Enterprise Cloud.