[BUG] <title>

[prajapatiankush967-a11y]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

---

title: npm-token
section: 1
description: Manage your authentication tokens

Synopsis

Description

This lets you list, create and revoke authentication tokens.

Listing tokens

When listing tokens, an abbreviated token will be displayed. For security purposes the full token is not displayed.

Generating tokens

When generating tokens, you will be prompted you for your password and, if you have two-factor authentication enabled, an otp.

Please refer to the docs website for more information on generating tokens for CI/CD.

Revoking tokens

When revoking a token, you can use the full token (e.g. what you get back from npm token create, or as can be found in an .npmrc file), or a truncated id. If the given truncated id is not distinct enough to differentiate between multiple existing tokens, you will need to use enough of the id to allow npm to distinguish between them. Full token ids can be found on the npm website, or in the --parseable or --json output of npm token list. This command will NOT accept the truncated token found in the normal npm token list output.

A revoked token will immediately be removed from the registry and you will no longer be able to use it.

Configuration

See Also

• npm adduser
• npm registry
• npm config
• npmrc
• npm owner
• npm whoami
• npm profile

Expected Behavior

No response

Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...

Environment

• npm:
• Node.js:
• OS Name:
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here