`npm audit` 不断返回“您配置的注册表 (https://registry.npmjs.org/) 不支持审核请求。”。 我如何让它再次工作？

Question

Here is the error I get:

npm ERR! code ENOAUDIT
npm ERR! audit Your configured registry (https://registry.npmjs.org/) does not support audit requests.

with the log file:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'audit' ]
2 info using npm@6.4.1
3 info using node@v10.12.0
4 verbose npm-session 65e7a3436fc1253b
5 timing audit compress Completed in 25ms
6 info audit Submitting payload of 217372 bytes
7 http fetch POST 503 https://registry.npmjs.org/-/npm/v1/security/audits 13252ms
8 verbose stack Error: Your configured registry (https://registry.npmjs.org/) does not support audit requests.
8 verbose stack     at Bluebird.all.spread.then.catch (/usr/local/lib/node_modules/npm/lib/audit.js:172:18)
8 verbose stack     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
8 verbose stack     at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
8 verbose stack     at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
8 verbose stack     at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
8 verbose stack     at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:689:18)
8 verbose stack     at Async._drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
8 verbose stack     at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
8 verbose stack     at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
8 verbose stack     at runCallback (timers.js:705:18)
8 verbose stack     at tryOnImmediate (timers.js:676:5)
8 verbose stack     at processImmediate (timers.js:658:5)
9 verbose cwd /Users/danielhasegan/workspace/code
10 verbose Darwin 18.2.0
11 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "audit"
12 verbose node v10.12.0
13 verbose npm  v6.4.1
14 error code ENOAUDIT
15 error audit Your configured registry (https://registry.npmjs.org/) does not support audit requests.
16 verbose exit [ 1, true ]

I tried multiple ideas found across github but I do not have any proxy or http-proxy set. both of those return null :

npm config get proxy
npm config get https-proxy

Any ideas? This is not transitory, ive been getting it for a while now. I find it weird I get 503 . It means something is wrong with my connection.

Answer 1

Try running npm update and then npm audit . This should fix the problem.

Answer 2

当你的package.json有类似"PACKAGE_NAME": "github:USERNAME/PACAKGE_NAME"或任何其他不同的模式而不是典型的模式时，你可以拥有它，即"PACKAGE_NAME": "PACKAGE_VERSION" 。

Answer 3

First

npm install -g npm

then

npm audit

may solve your problem

Answer 4

i have tried all the answers mentioned but no luck. it works for me only when i removed both node_modules and package-lock.json after that i run npm install and then npm audit fix then it worked

Answer 5

I found that the answer given at https://npm.community/t/your-configured-registry-https-registry-npmjs-org-does-not-support-audit-requests/3600/6 worked, where none of the above answers helped:

delete your node_modules folder then try running npm install --> npm update --> npm audit

Answer 6

对我来说，只有在删除package-lock.json并运行npm update我才能运行npm audit 。

Answer 7

I'm confident this is a service issue with the NPM servers. I got this same issue, across all projects, in CI and development machines. So unlikely to be environment or package.json issues.

Notice the error:

http fetch POST 503 https://registry.npmjs.org/-/npm/v1/security/audits 13252ms

A 503 is a server issue:

The HyperText Transfer Protocol (HTTP) 503 Service Unavailable server error response code indicates that the server is not ready to handle the request.

Common causes are a server that is down for maintenance or that is overloaded. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time for the recovery of the service.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503

Simply waiting some time for whatever issue in the NPM service to be resolved fixed it for me. I suspect all these answers about updating npm, removing package-lock.json , deleting node_modules simply cause a delay for the service issues to resolve.

Answer 8

解决此问题的最安全方法是删除文件夹node_modules和package-lock.json并运行npm install

Answer 9

For me problem was in my npm profile and none of the above mentioned fixes worked.

Doing the following fixed the issue.

1: Install npmrc if it's not already available

npm i npmrc -g

2: Create a profile for the public NPM registry

npmrc -c npm

npm config set registry https://registry.npmjs.com/

Reference : https://docs.open-registry.dev/known-issues-and-workarounds/

Answer 10

We have a private registry mentioned in the .npmrc file that was preventing the audit. I just commented that out to run the audit.

I would not recommend npm update , especially on enterprise applications like mine, that have hundreds of modules and tens of internal and external dependencies.