Skip to content

Conversation

@lennym
Copy link
Contributor

@lennym lennym commented Aug 1, 2018

I have created a wrapper for it, because npm audit itself always fails if any vulnerabilities are present, and we don't want to fail on low or moderate vulnerabilities. This issue has been PR'ed in npm, so if/when npm/cli#31 is merged and released then the command can be swapped for a basic npm audit.

lennym added 2 commits August 1, 2018 16:20
I have created a wrapper for it, because `npm audit` itself _always_ fails if _any_ vulnerabilities are present, and we don't want to fail on low or moderate vulnerabilities. This issue has been PR'ed in npm, so if/when npm/cli#31 is merged and released then the command can be swapped for a basic `npm audit`.
@lennym lennym force-pushed the improvement/npm-audit-in-ci branch from 9a325f5 to a0f2017 Compare August 1, 2018 15:31
@lennym
Copy link
Contributor Author

lennym commented Aug 1, 2018

Example CI output:

Scanning for vulnerabilities...
low:        1
moderate:   0
high:       0
critical:   0

No vulnerabilities of level "high" or above detected.

@joefitter joefitter merged commit f96d025 into master Aug 1, 2018
@joefitter joefitter deleted the improvement/npm-audit-in-ci branch August 1, 2018 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants