score:28

Accepted answer

this is a result of the new npm version including the audit command.

it isn't some new issue with the angular cli, npm just introduced new functionality in npm to warn users about vulnerabilities in the packages they're installing - so there's no "new" vulnerability in angular, it's just that now npm is now warning you about vulnerabilities that already existed:

https://blog.npmjs.org/

most of the issues stem from karma, so it'd need to be fixed there for the angular team to pull in a new karma version karma-runner/karma#2994

score:-4

i had the same problem while running this command:

npm install ngx-bootstrap --save

...and solved it by running the command prompt as administrator.

so open the command prompt as administrator and then try again. hopefully it will work.

score:1

i faced the same issue while installing react-native navigation, using:

npm install react-navigation

for me, npm audit-fix didn't worked well. npm use to have some limitations. for me, yarn worked:

yarn add <package-name>

score:2

i had the same issue and log was like below:

testing binary
binary is fine
added 1166 packages from 1172 contributors and audited 39128 packages in 112.505s
found 1 high severity vulnerability

i executed the below command and it was fixed.

npm audit fix

log shows as below:

testing binary
binary is fine
+ @angular-devkit/build-angular@0.11.4
added 18 packages from 47 contributors, removed 14 packages and updated 52 packages in 64.529s
fixed 1 of 1 vulnerability in 39128 scanned packages

score:7

even after running npm audit fix if it is not fixed, then to proceed i think you should turn off npm audit. use below command to turn off npm audit.

when installing a single package.

npm install example-package-name --no-audit

to turn off npm audit when installing all packages

npm set audit false

it will set the audit setting to false in your user and global npmrc config files.

for reference visit : turn-off-npm-audit

hope it will help and you can proceed to your work :) happy codding

score:21

if you have ran npm audit and got vulnerabilities, then you can have different scenarios:

security vulnerabilities found with suggested updates

  • run the npm audit fix subcommand to automatically install compatible updates to vulnerable dependencies.

  • run the recommended commands individually to install updates to vulnerable dependencies. (some updates may be semver-breaking changes; for more information, see "semver warnings".)

security vulnerabilities found requiring manual review

  • if security vulnerabilities are found, but no patches are available, the audit report will provide information about the vulnerability so you can investigate further.

source: reviewing and acting on the security audit report


Related Query

More Query from same tag