Added support for severity #41
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 23, 2020 20:49
…pecified dont cause grunt task to fail. Not passing a severity in configuration keeps the former behavior of the task (i.e., any vulnerability triggers failure).
ilattinnj
approved these changes
Jun 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Usage:
On Gruntfile add severity in retire configuration to indicate the minimum severity that will cause grunt task to fail. Note that all vulnerabilities are still displayed for reference.
Not passing the severity value will trigger default of 'all' which keeps the task behaving as it is now; i.e., any vulnerability found will cause grunt to fail regardless of the severity.
On the other hand, severity of 'none' will cause grunt task to always pass.