`Not found`

npm registry · GET /{package} · HTTP 404

Status: ✅ verified:server:prod · first seen 2026-10-31 · last confirmed 2026-10-31 · 1 confirmation from 1 vantage

GET /{package} for a package that does not exist returns HTTP 404 with {"error": "Not found"}; a name spelled with uppercase letters (/Left-Pad) is the same 404, not a redirect to the lowercase package.

What to do

No client-side fix known (by design).

Example

What probe af:npm-registry:probe:package-not-found sends (prod) and what it checks in the answer.

Step 1 → HTTP 404:

GET https://registry.npmjs.org/agent-facts-probe-no-such-package

Step 2 → HTTP 404:

GET https://registry.npmjs.org/Left-Pad

Response (only what the probe asserts; other fields omitted):

HTTP 404

{
  "error": "Not found"
}

Dimensions

env: prod · plan: any · region: any · account_state: anonymous

Evidence

Probe af:npm-registry:probe:package-not-found (declarative, source)

Observations: none from reporters yet.

Related errors

Not Found · GET /-/package/{package}/dist-tags · HTTP 404
Not Found · GET /{package}/{version} · HTTP 404
version not found: 0.0.99 · GET /{package}/{version} · HTTP 404

Machine access

Match signature (what check() matches): not found

curl -s https://apifacts.dev/v0/check \
  -H 'content-type: application/json' \
  -d '{"target":{"method":"GET","url":"https://registry.npmjs.org/{package}"},"error":{"status":404,"body_excerpt":"not found"}}'

YAML: facts/npm-registry/package-not-found-404.yaml

Data: CC BY 4.0 · apifacts registry · This page is generated; edit the YAML, not the page.