`Not Found`

npm registry · GET /{package}/{version} · HTTP 404

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

GET /{package}/{version} for a package that does not exist returns HTTP 404 with the bare JSON string "Not Found"; an unencoded scoped name (/@scope/name) lands on the same path shape and returns {"error": "Not found"}.

What to do

No client-side fix known (by design).

Example

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

Step 1 → HTTP 404:

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

Step 2 → HTTP 404:

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

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:missing-package-two-segments (declarative, source)

Observations: none from reporters yet.

Related errors

version not found: 0.0.99 · GET /{package}/{version} · HTTP 404
Not Found · GET /-/package/{package}/dist-tags · HTTP 404
Not found · GET /{package} · 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}/{version}"},"error":{"status":404,"body_excerpt":"not found"}}'

YAML: facts/npm-registry/missing-package-version-path-404.yaml

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