Requiring 2FA for package publishing and settings modification

See Details

Table of contents

All packages now require two-factor authentication (2FA) for creating and publishing packages. For more information, see "Configuring two-factor authentication".

You may also choose to publish with granular access tokens with bypass 2FA enabled. This lets you configure tokens in a CI/CD workflow, but requires two-factor authentication from interactive publishes.

For CI/CD workflows, consider using trusted publishing, which provides secure, token-free publishing that automatically enforces strong authentication without requiring manual token management.

Important notes about granular access tokens:

Bypass 2FA configuration is set at token creation
When bypass 2FA is disabled: The system will check account-level and package-level settings to determine if 2FA is required
When bypass 2FA is enabled: The token will bypass all 2FA requirements at all times, regardless of account-level or package-level 2FA settings
When Require two-factor authentication and disallow tokens is selected at the package level, granular access tokens cannot be used regardless of their bypass 2FA setting

Configuring two-factor authentication

On the npm "Sign In" page, enter your account details and click Sign In.
Navigate to the package on which you want to require a second factor to publish or modify settings.
Click Settings.
Under "Publishing access", select the requirements to publish a package.

Note: All packages now require either two-factor authentication or a granular access token with bypass 2FA enabled to publish. This is the default setting for all new packages.
Require two-factor authentication or granular access tokens (Default)
With this option, maintainers must have two-factor authentication enabled for their account. If they publish a package interactively, using the npm publish command, they will be required to enter 2FA credentials when they perform the publish. However, maintainers may also create a granular access token with bypass 2FA enabled and use that to publish. A second factor is not required when using these specific token types, making them useful for continuous integration and continuous deployment workflows. 2. Require two-factor authentication and disallow tokens
With this option, a maintainer must have two-factor authentication enabled for their account, and they must publish interactively. Maintainers will be required to enter 2FA credentials when they perform the publish. Granular access tokens cannot be used to publish packages, regardless of their bypass 2FA setting.
Click Update Package Settings.

Edit this page on GitHub

9 contributors

Last edited by karenjli on November 5, 2025