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.
I wanted to filter
npm
audit output to see only serious issues, and while searching for how to do that, I landed at issue #13.I saw @welwood08 had said he would take care of it, however his revision was lost in some migration, apparently, and some further searching led me to his more recent comment, inviting anyone else to take over where he left off.
This is the result of my attempt to do so, taking his feature branch and comparing it file by file to the
latest
in this repository.I might be way off when it comes to addressing some concern(s) which people more familiar with npm and its family of projects would know off-hand, if so apologies, but perhaps this can be useful anyhow. Let me know what might need to be done before it could be accepted and I'll be glad to take some additional passes at it.