Skip to content

When an install is blocked

When Provenix won't serve something, your install fails with an HTTP status. This page explains each one and what to do.

Read the full message

npm shows only a short code, for example:

npm error code E451
npm error 451 Unavailable For Legal Reasons - GET https://npm.example.com/left-pad - package_not_approved

Provenix's full answer has more: when the package should be available, and a link to it in the console. Fetch the same URL with your token to see it:

curl -sS -H "Authorization: Bearer $PROVENIX_NPM_TOKEN" \
  https://npm.example.com/left-pad | jq

451: not approved yet

package_not_approved

Nobody in your workspace has used this package before. Provenix has started fetching and scanning it, and the response says when it expects the package to be available:

{
  "error": "package_not_approved",
  "package": "left-pad",
  "estimated_available_at": "2026-11-29T10:00:00Z",
  "console_url": "https://provenix.example.com/packages/left-pad"
}

What to do:

  • Check the name. A typo (lodahs) or a lookalike package triggers this too.
  • Wait, if you can. A brand-new package is held for 7 days by default unless your workspace's policy says otherwise.
  • Ask for it sooner: request an expedited review of the version you need.

You don't need to run the install again to "start" anything: discovery is already queued.

version_not_approved

Provenix knows the package, but this version isn't approved in your workspace. It's still being scanned, waiting out its hold or waiting for a reviewer, or a reviewer has rejected it. The response names the version and includes request_review_path, the path to request an expedited review:

{
  "error": "version_not_approved",
  "package": "lodash",
  "version": "4.17.22",
  "estimated_available_at": "2026-11-25T09:00:00Z",
  "request_review_path": "/api/v1/packages/lodash/versions/4.17.22/request-review"
}

You usually see this when the lockfile or package.json pins an exact version that isn't approved. If a range would do (^4.17.0), Provenix resolves it to the newest approved version instead.

If the version stays blocked, open console_url (or ask your reviewers): the console shows where it is in review, and the note on any rejection.

403 policy_denied: your policy blocks it

Your workspace's policy denies this package or version outright, for example a version on a deny list. The response's message says which rule applied, and the response carries X-DF-Policy-Block: true. Waiting won't help: choose another version, or ask your Provenix admin about the policy.

404: no such version

Provenix has no record of that version: it doesn't exist upstream, or the name or version is mistyped.

429: too many new packages

Each client can trigger only a limited number of unknown packages per hour (10 by default), and so can each workspace. The response includes Retry-After. This usually means a script is installing many packages Provenix hasn't seen. Ask your Provenix admin to seed them instead.

401: the token isn't accepted

The token is missing, mistyped, or has been rotated or deactivated. Check npm whoami, then the PROVENIX_NPM_TOKEN variable in that environment.

503: Provenix can't decide right now

Provenix couldn't check its own records or policy, for example during a database outage, so it refuses to serve rather than guess. The response includes Retry-After. Retry the install; if it keeps happening, tell whoever runs Provenix.

502 with X-DF-Integrity-Mismatch

The upstream registry returned different bytes for a version than the ones Provenix scanned. Provenix refuses to serve them. Report it to your Provenix reviewers: it can mean the package was tampered with upstream.