GitHub puts a human checkpoint before npm packages go public

GitHub has added an npm publishing control that treats a package release as a security event, not just the last routine step in a CI/CD script. According to The Hacker News, the feature is called staged publishing and is now generally available on npm. Its rule is direct: before a package becomes publicly available for installation, a human maintainer must explicitly approve the release and pass a two-factor authentication challenge.

That is not a cosmetic interface change. npm is one of the central distribution layers of the modern JavaScript ecosystem, and a package attack does not need to compromise every developer machine directly. One popular package, one compromised maintainer account, or one automated release path can be enough to push malicious code downstream into projects that install dependencies as routine infrastructure.

Staged publishing adds friction at the point where friction makes sense. If publication previously looked like the final automated step in a pipeline, the new control requires explicit human confirmation before public distribution. GitHub is not solving all open-source security with one feature, but it is closing a specific window: the scenario where a compromised token, account, or automated process moves a new version straight into the public install flow.

The two-factor requirement is not decorative here. npm’s 2FA documentation frames the second factor as protection for sensitive account actions, and package publication clearly belongs in that class. In the staged publishing model, 2FA becomes the threshold between a prepared release and actual distribution. It does not prevent every maintainer mistake, but it means an attacker needs more than a silent automated credential.

The broader direction matters too. npm already has controls around identity and access, including access tokens, while GitHub has pushed more verifiable build chains through npm provenance, where a package release can be tied back to source and build context. Staged publishing fits the same logic: less blind trust in automation, more explicit checkpoints around distribution.

For maintainers, the cost is another step in the release process. For the ecosystem, the benefit is a clearer security boundary around the moment a package moves from privately prepared artifact to public dependency. This will not stop every software supply chain attack. But it places a rational barrier at the point where damage can spread fastest: between a publish action and the first installs inside other people’s projects.