npm audit: some vulnerabilities require your attention to resolve
See original GitHub issueTo reproduce:
npm init
npm i aws-iot-device-sdk -S
npm audit fix
npm audit
Npm audit security report:
found 1 low severity vulnerability in 430 scanned packages
1 vulnerability requires manual review. See the full report for details.
PR is there for a while: https://github.com/aws/aws-iot-device-sdk-js/pull/315
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Auditing package dependencies for security vulnerabilities
Security audits help you protect your package's users by enabling you to find and fix known vulnerabilities in dependencies that could cause data...
Read more >Some vulnerabilities require your attention to resolve - minimist
Hi,. I am running a pipeline using the lambci/lambda:build-python3.6. The process install the packages/dependencies below:
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 npm vulnerabilities manually? - Stack Overflow
I believe that version shown in "_id", not in "_from", so versions are correct but vulnerability still appear in audit list. I'm still...
Read more >How to Fix Security Vulnerabilities with NPM - IFS Blog
Try running npm update command. It will update all the package minor versions to the latest and may fix potential security issues. If...
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 Free
Top 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

It’s being integrated internally and tested. At the moment, this GitHub repository is just a mirror, so the PR would just be overwritten.
2.2.4 has been published to npm just now.