npm / npm

pnpm audit Returns 410 Endpoint Retired Use Bulk Advisory Endpoint Instead

Fix pnpm audit 410 error after npm registry retired the v1 security audits endpoint Includes evidence for npm troubleshooting demand.

Source-backed Last updated May 16, 2026 2 sources Needs local verification

Category: npm
Error signature: ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."}
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 16, 2026
Verification status: Source-backed
Evidence: 2 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for npm, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."} is a npm failure pattern reported for developers trying to fix pnpm audit 410 error after npm registry retired the v1 security audits endpoint. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Stack Overflow user reports pnpm audit suddenly returns 410 error because npmjs.org retired the /-/npm/v1/security/audits endpoint. Breaking change affecting all pnpm/npm audit users. Requires migration to new bulk advisory endpoint. High impact: security audit workflow broken for entire npm ecosystem.

Common causes

Stack Overflow user reports pnpm audit suddenly returns 410 error because npmjs.org retired the /-/npm/v1/security/audits endpoint. Breaking change affecting all pnpm/npm audit users. Requires migration to new bulk advisory endpoint. High impact: security audit workflow broken for entire npm ecosystem.

Quick fixes

Confirm the exact error signature matches ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."}.
Check the npm account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."} exactly before applying the quick fix.
Compare the failing environment with npm versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."} mean in npm?

ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."} indicates the workflow described by "pnpm audit Returns 410 Endpoint Retired Use Bulk Advisory Endpoint Instead" failed in a npm context. Start by confirming the exact signature and the component that emitted it.

What should I check first for ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."}?

Check whether this cause matches your environment: Stack Overflow user reports pnpm audit suddenly returns 410 error because npmjs.org retired the /-/npm/v1/security/audits endpoint. Breaking change affecting all pnpm/npm audit users. Requires migration to new bulk advisory endpoint. High impact: security audit workflow broken for entire npm ecosystem.

Is the ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."} guidance source-backed?

The "pnpm audit Returns 410 Endpoint Retired Use Bulk Advisory Endpoint Instead" page is labeled source-backed. It has 2 public source URLs from registry.npmjs.org, stackoverflow.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."}?

For "pnpm audit Returns 410 Endpoint Retired Use Bulk Advisory Endpoint Instead", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging ERR_PNPM_AUDIT_BAD_RESPONSE — The audit endpoint (at https://registry.npmjs.org/-/npm/v1/security/audits) responded with 410: {"error":"This endpoint is being retired. Use the bulk advisory endpoint instead."}?

For "pnpm audit Returns 410 Endpoint Retired Use Bulk Advisory Endpoint Instead", collect the failing npm command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.