What This Error Means
npm was authenticated, but the registry returned 403 Forbidden because your account lacks permission for that package, scope, or action.
How to Fix It
Check which registry npm is using:npm config get registry
If the package is scoped, verify scope registry mapping in .npmrc (example: @your-scope:registry=...).
Confirm the registry identity:npm whoami (it should print a username for that registry).
If you are installing a private package, confirm your account has access (org membership / package access rules).
If you are publishing, confirm you are a maintainer:npm owner ls <pkg> and verify you have publish permission.
If you use GitHub Packages or another private registry, confirm the token has the correct scopes/permissions for that registry.
Retry with logs:npm --verbose (it shows which host returned 401/403).
Why It Happens
Your .npmrc token is missing, expired, or scoped to the wrong registry host.
You are installing a private package but you are not authenticated for that scope/registry.
The token is valid but lacks permission (forbidden) for the requested package or operation.
How to Verify
Run npm whoami and confirm it succeeds.
Re-run the original command and confirm the registry no longer returns 401/403.
Manual authentication checks
Print effective config:npm config list -l (look for registry and auth entries).
Check .npmrc precedence (project, user, global) to ensure you are editing the right file.
Examples
npm ERR! code E403
npm ERR! 403 Forbidden: lite-server@latestHow npm uses registry credentials
npm sends requests to the configured registry using credentials from .npmrc.
Registry hosts treat tokens differently (npmjs vs GitHub Packages vs private registries).
A mismatched registry host/token pairing is a common cause of 401/403.
Prevention Tips
Use dedicated tokens for CI and rotate them periodically.
Keep .npmrc registry routing explicit for scoped packages.
Use a proxy/cache registry to reduce auth surprises between environments.
Where This Can Be Triggered
github.com/npm/cli/blob/417daa72b09c5129e7390cd12743ef31bf3ddb83/lib/utils/get-identity.js
This is a registry authentication call path. Auth errors like this code appear when the registry returns 401/403 for these endpoints. - GitHub
// No username, but we have other credentials; fetch the username from registry
if (creds.token || creds.certfile && creds.keyfile) {
const registryData = await npmFetch.json('/-/whoami', { ...opts })
if (typeof registryData?.username === 'string') {
return registryData.username
}