Security vulnerability (High Severity) in js-yaml dependency
See original GitHub issueDescription
js-yaml needs to be updated to >= 3.13.0. The current version has a mod-severity security vulnerability.
Steps to reproduce
- Install latest
- Run npm audit / yarn audit
Debug Logs
expand to view
Not applicable
Environment
- OS: This applies in all environments
- Node.js: 1
lint-staged
: Latest: 8.1.5
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
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 >Github alert: "One of your dependencies has a security ...
(from Github) which says: “Known high severity security vulnerability detected in js-yaml < 3.13.1 defined in package-lock.json. package-lock.
Read more >How to Fix Security Vulnerabilities with NPM - IFS Blog
Npm scans through our dependencies to check for possible security vulnerabilities that exist in our dependency tree.
Read more >How to Fix Vulnerability Issues in Node.JS & Gulp with NPM ...
In this video I show you how to use NPM Override and NPM Audit Fix to resolve vulnerability issues in Node. JS, Gulp,...
Read more >js-yaml - Issues - Socket - Socket.dev
Start using Socket to analyze js-yaml and its 2 dependencies to secure your app from ... Contains a high severity Common Vulnerability and...
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
🎉 This issue has been resolved in version 8.1.7 🎉
The release is available on:
Your semantic-release bot 📦🚀
Yes, I believe it should be enough.