Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

`npm audit` keeps returning "Your configured registry (https://registry.npmjs.org/) does not support audit requests.". How do I make it work again?

Tags:

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 [email protected] 3 info using [email protected] 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.

like image 448
Daniel Hasegan Avatar asked Mar 02 '19 00:03

Daniel Hasegan


People also ask

What is npm audit fix?

The npm audit fix command will exit with 0 exit code if no vulnerabilities are found or if the remediation is able to successfully fix all vulnerabilities. If vulnerabilities were found the exit code will depend on the audit-level configuration setting.

How do I find npm registry URL?

You can show the registry of a specific package with the npm view command. When you use npm config get registry you will see the default registry.

What is registry Npmjs?

The public npm registry is a database of JavaScript packages, each comprised of software and metadata. Open source developers and developers at companies use the npm registry to contribute packages to the entire community or members of their organizations, and download packages to use in their own projects.

How do I find audit reports in npm?

Running a security audit with npm audit Note: The npm audit command is available in npm@6. To upgrade, run npm install npm@latest -g . The npm audit command submits a description of the dependencies configured in your package to your default registry and asks for a report of known vulnerabilities.


1 Answers

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

like image 132
Sohail Avatar answered Oct 13 '22 01:10

Sohail