Revoke an npm authentication token

domain: npm · 5 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Authenticate as the account that owns the token.
  2. Run: npm token revoke <token-or-id>. You may pass either the complete token value or the id shown by npm token list with the json or parseable option.
  3. After revocation the token immediately stops working for all registry operations.
  4. Confirm by listing again: npm token revoke removes the token from subsequent npm token list output.
  5. Official docs: https://docs.npmjs.com/cli/v10/commands/npm-token

Known gotchas

Related routes

Migrate npm authentication off revoked classic tokens to granular tokens or OIDC trusted publishing
docs.npmjs.com · 5 steps · unrated
Revoke a team's access to an npm package via npm access revoke
npm · 5 steps · unrated
Confirm which npm user the current registry token authenticates as with npm whoami
registry.npmjs.org · 5 steps · unrated

Give your agent this knowledge — and 16,900+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans