You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @ruyadorno isn't the case that in latest version 7
For example
npm audit
6 vulnerabilities (4 low, 2 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
npm audit fix
now it's just showing up to date and at the bottom severity vulnerabilities
up to date, audited 509 packages in 3s
1 package is looking for funding
run `npm fund` for details
# npm audit report
minimist <0.2.1 || >=1.0.0 <1.2.3
Prototype Pollution - https://npmjs.com/advisories/1179
fix available via `npm audit fix --force`
Will install express-generator@4.2.0, which is a breaking change
node_modules/minimist
mkdirp 0.4.1 - 0.5.1
Depends on vulnerable versions of minimist
node_modules/express-generator/node_modules/mkdirp
express-generator >=4.8.0
Depends on vulnerable versions of mkdirp
node_modules/express-generator
3 low severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Currently reify-output will also print the number of vulns per type, e.g:
It should also implement this style of count per type for
npm audit fix
output.Current output:
Proposed output:
from: npm/rfcs#266
The text was updated successfully, but these errors were encountered: