Menu
This recently broke and I do not know what I might have done to break it beyond adding some additional dependencies. I am using https://registry.npmjs.org/ (the default). The relevant portion of the log file is below. Has anyone seen something similar? I've only seen this referenced in some old bug reports.
6 info audit Submitting payload of 66980 bytes
7 http fetch POST 500 https://registry.npmjs.org/-/npm/v1/security/audits 548ms
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 (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\lib\audit.js:172:18)
8 verbose stack at tryCatcher (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\util.js:16:23)
8 verbose stack at Promise._settlePromiseFromHandler (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:512:31)
8 verbose stack at Promise._settlePromise (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:569:18)
8 verbose stack at Promise._settlePromise0 (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:614:10)
8 verbose stack at Promise._settlePromises (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:689:18)
8 verbose stack at Async._drainQueue (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:133:16)
8 verbose stack at Async._drainQueues (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:143:10)
8 verbose stack at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\micha\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:17:14)
8 verbose stack at runCallback (timers.js:694:18)
8 verbose stack at tryOnImmediate (timers.js:665:5)
8 verbose stack at processImmediate (timers.js:647:5)
9 verbose cwd C:\src\studio-template
10 verbose Windows_NT 10.0.17134
11 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\micha\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "audit"
12 verbose node v10.11.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.
900
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.
Today, npm audit is broken by design. Beginners, experienced developers, maintainers, security departments, and, most importantly — our users — deserve better.
The npm audit command scans your project for security vulnerabilities and provides a detailed report of any identified anomaly. Performing security audits is an essential part in identifying and fixing vulnerabilities in the project's dependencies.
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.
Apparently, this was a transitory error. I'm guessing npmjs had issues on their end.
109
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
