-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add module-ignore flag #71
Conversation
expect(result).to.have.length(8).and.deep.equal([1165, 1890, 985, 1213, 1654, 2000, 2001, 2100]); | ||
expect(result).to.have.length(7).and.deep.equal([1165, 1890, 985, 1213, 2000, 2001, 2100]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mock data had some data points that had gone past the set expiration date, requiring the test fixes in this file
+1 on this update. Would help us tremendously. Thanks @alexburkowskypolysign |
this is a great feature, thank you for contributing @alexburkowskypolysign ! |
You are very welcome @jeemok! Thanks for merging |
will it support if we include in .nsprc file as well ? |
@Sujay-shetty not currently, but definitely sounds like a good feature. Can you help to create a new issue and we can track it from there? |
Description
To address feature request: #69
This fixes the issue where vulnerabilities disputed by package owners causes ever changing vulnerability ids in the audit report. In my repo I have to a seemingly infinite number of ids to my
.nsprc
to manage the currently disputedlodash
issue:Having a single flag to ignore
lodash
rather than w/e next id pops up for the same vulnerability is a huge time saver in a team environment :).TODO
Screenshots
Tested via
npm link
No flags, remove nsprc code for lodash (1 module):
-m
flag 1 module:--module-ignore
flag 1 module:--module-ignore
flag 2 modules (removedlodash
andhermes-engine
ids fromnsprc
):@jeemok @GrzesiekP @IPWright83