GitHub Introduces Staged Publishing for npm with 2FA Approval
Enable staged publishing for npm packages and require 2FA approval before releases go public.
Activate staged publishing on your npm projects and enforce 2FA for release approvals.
Summary
GitHub has rolled out new controls for npm to improve the security of the software supply chain, giving maintainers the ability to explicitly approve a release prior to the packages becoming publicly available for installation. The feature, called staged publishing, is now generally available on npm. It mandates that a human maintainer pass a two‑factor authentication (2FA) challenge to approve the release. Staged publishing allows maintainers to review and approve each release before it is published, reducing the risk of malicious code being distributed. The new controls aim to strengthen the integrity of npm packages and protect developers from supply‑chain attacks. The feature is designed to be easy to enable for existing npm projects. Organizations should enable staged publishing to add an extra layer of security to their release process.
Key changes
- GitHub introduces staged publishing for npm
- Maintainers must approve releases before public availability
- Feature requires 2FA challenge
- Now generally available
- Improves supply chain security
- Allows explicit release control