-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packages audit throw high and critical vulnerabilities for runtime dependencies #191
Comments
I've checked these packages and most of them are only being used while packaging the project. So these form no risk. We need to check if we can update direct dependencies like modernizr & handlebars. Btw I didn't see swiper coming back from vulnerable dep list, is this a project specific dependency ? |
@jesse-mm yes, Swiper is a project specific dependency, sorry I didn't filter that out! |
How can I evaluate what kind of actual danger the high/critical vulnerabilities found in |
The vulnerabilities are posing a risk mostly when compiling on the build server / or locally. In that case to exploit it an attacker would need to have access to the code / or the machine where it's built on. In the latter case the damage is already done. I would suggest to read up on this blog post https://overreacted.io/npm-audit-broken-by-design/ |
Running "muban-core": "^2.1.2".
26 vulnerabilities found - Packages audited: 162
Severity: 8 Low | 4 Moderate | 11 High | 3 Critical
What can we do about this?
Complete audit here:
The text was updated successfully, but these errors were encountered: