Skip to content
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

provide severity option #39

Closed
wants to merge 1 commit into from

Conversation

llaenowyd
Copy link

@llaenowyd llaenowyd commented Apr 29, 2019

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.

@llaenowyd llaenowyd changed the title revise welwood08 exceptions branch to latest provide severity option Apr 29, 2019
@llaenowyd
Copy link
Author

npm/cli#159

@isaacs
Copy link
Contributor

isaacs commented May 8, 2020

Closing out all issues and PRs from 2018 and 2019, since this module has been fundamentally refactored for version 2 (npm version 7). Happy to reopen if this is still a thing worth exploring (and it'll probably be easier now if so).

@isaacs isaacs closed this May 8, 2020
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.

2 participants