Open HerreraG opened 6 years ago
Unfortunately I have the same problem
I noticed this as well, I started a pr (branched off my fork) and started looking, however a lot of the vulnerabilities have to do with karma, Karma Issue, which is waiting for Log4js to update, which 2 days ago just fixed its vulnerabilities Log4js Issue. I'll keep track over the next couple days to see how this moves.
Hello, do you have any news on this issue? I now have 27 vulnerabilities with the same environment.
Log4js Issue is resolved, still waiting on karma, They did a 2.x version release, the Updated log4js required karma to drop nodev4, which they have a merged fix, but it will start in v3 of karma which hasn't been released just yet,
https://github.com/akveo/ngx-admin/pull/1822 Created PR, fixes 90% of issues
Hello!
Just ran npm install on a fresh clone today and now it's 54 vulnerabilities.
added 1757 packages from 1379 contributors and audited 23286 packages in 31.621s found 54 vulnerabilities (17 low, 22 moderate, 15 high)
Hello, I have updated my own and have 0, I'll pull the official one down and finish getting everything cleared out. Then just need to get the pr merged.
Still exists on v3.0.0?
added 1998 packages from 1382 contributors and audited 25850 packages in 101.583s
found 42 vulnerabilities (17 low, 11 moderate, 14 high)
run `npm audit fix` to fix them, or `npm audit` for details
Issue type
I'm submitting a ... (check one with "x")
Issue description
Current behavior: When I run npm install npm informs me that it found 22 vulnerabilities. I leave report.
found 22 vulnerabilities (11 low, 5 moderate, 6 high) run
npm audit fixto fix them, or
npm auditfor details
Expected behavior: Not have high vulnerabilities.
Steps to reproduce: Clone project starter-kit and run npm install
Other information:
Thank you and excuse me for my English. Regards