41 vulnerabilities (34 moderate, 7 high)
See original GitHub issue- Laravel Framework 8.46.0
- Laravel Mix Version: npm list --depth=0
├── laravel-mix@6.0.19 ├── lodash@4.17.21 └── postcss@8.3.0
- Node Version (
node -v
): v15.10.0 - NPM Version (
npm -v
): 7.6.0 - OS: MacOSx Big Sur version 11.4, Apple silicon
Description:
Just installed fresh Laravel, and run npm install I am getting this error: 41 vulnerabilities (34 moderate, 7 high)
Steps To Reproduce:
Install new laravel instance Run npm install
Issue Analytics
- State:
- Created 2 years ago
- Reactions:13
- Comments:10
Top Results From Across the Web
41 vulnerabilities (34 moderate, 7 high) · Issue #2999
Description: Just installed fresh Laravel, and run npm install. I am getting this error: 41 vulnerabilities (34 moderate, 7 high).
Read more >Found 4 vulnerabilities on npm install
I got 164 vulnerabilities found - Packages audited: 20493 (312 dev, 1044 optional). Severity: 110 low | 35 moderate | 19 high. –...
Read more >Don't be alarmed by vulnerabilities after running NPM Install
Results of running NPM install with a list of vulnerabilities found in packages ... One with a moderate status and one with a...
Read more >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 >How to Fix Security Vulnerabilities with NPM
Fixing security vulnerabilities is essential to the the success of a software solution.
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
So I updated some stuff in our
master
branch over the weekend however, even if we tag a release, it won’t fix some vulnerabilities still present in dependencies.@types/browser-sync
pulling in an old version of chokidar.resolve-url-loader
pulls in a vulnerable version of postcss (when it should be a peer dep).We should still tag a new release though. I’ll see if we can do that soon.
so far my side only 7 high vulnerabilities from css-what from svgo so it is getting better