Fix: npm pkgs vulnerabilities
See original GitHub issueIssue or Feature Request Description: What’s the update to fix high and critical pkgs vulnerabilities?
found 44 vulnerabilities (4 low, 6 moderate, 32 high, 2 critical) in 61143 scanned packages
run `npm audit fix` to fix 18 of them.
16 vulnerabilities require semver-major dependency updates.
10 vulnerabilities require manual review. See the full report for details.
Thank you 🙏
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Auditing package dependencies for security vulnerabilities
Fix the vulnerability · Check the "Path" field for the location of the vulnerability. · On the npm public registry, find the package...
Read more >Fixing security vulnerabilities in npm dependencies in less ...
2.1) To fix any dependency, you need to first know which npm package depends on that. npm audit. This will tell you the...
Read more >How to Fix Your Security Vulnerabilities with NPM Overrides
Running npm update did not change the number of vulnerable packages and strangely npm audit fix added another vulnerability.
Read more >How to fix npm vulnerabilities manually? - node.js
Do a sanity check; In case it's a real problem, check the repository of vulnerable package for existing issues and PRs; In case...
Read more >How To Fix Vulnerable npm Packages Quickly and ...
The Challenge: Keeping Open Source Components Secure · Mend Research: Vulnerable npm Packages · Mend Insights: Fixing npm Vulnerabilities.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, but in Workbox v6, which raises the minimum required version of Node to v10.
We did a broad dependency version bump for Workbox v6.0.0-alpha.1, which is available for testing now. We’ll do another bump prior to the next alpha release.
Resolving all these issues while still maintaining compatibility with Node v8, which is what Workbox v5 supports, has proven infeasible in the past.
#2480 and #2481 should hopefully take care of things for v6.
Those PRs address dependencies used by
workbox-build
,workbox-cli
, andworkbox-webpack-plugin
.