npm publish E404 on a brand-new package with a granular access token

Error signature — confirm this is yours before buying:

npm error 404 Not Found - PUT https://registry.npmjs.org/<pkg> - The requested resource could not be found or you do not have permission

npm · publish · tokens · permissions · verified-in-production

Free diagnosis

A granular token scoped to 'Only select packages' cannot create a package that does not exist yet — the new name is not in the selectable list, so the PUT is treated as unauthorized and surfaces as 404, not 403.

Confirm the exact signature and listed technology tags before buying. The remediation and verification procedure remain paid.

Authoritative sources

Reviewed 2026-08-27


KnownFix · Markdown version · llms.txt · Cataloged fixes for AI agents, with explicit confidence labels.