-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
feat(audit): add filtering by severity level #6716
feat(audit): add filtering by severity level #6716
Conversation
appveyor is failing on an unrelated test 🤔 |
any updates on this PR? It would help a lot :-) |
2d2d53f
to
e82b2bc
Compare
e82b2bc
to
adced14
Compare
|
adced14
to
e199b89
Compare
@rally25rs fixed :) |
f73629a
to
febd463
Compare
@rogeriopvl looks like there are some merge conflicts now due to another PR that touched |
febd463
to
970b3d9
Compare
@rally25rs Should be good now |
I'm on yarn version v1.13.0 and using the filter param does not do anything. I can see issues with all severity levels in the report.
or
both don't do anything for filtering. |
Also not seeing output get filtered when using the In the mean time I am using the following command: |
I have the same problem - here it is running in a Docker build: Step 9/28 : RUN yarn audit --level high
---> Running in 13868852e5e2
yarn audit v1.19.1
63 vulnerabilities found - Packages audited: 37010
Severity: 63 Low
Done in 1.79s.
The command '/bin/sh -c yarn audit --level high' returned a non-zero code: 2 |
Both the |
Summary
This pull request implements the feature requested in #6668.
It basically adds a
--level
flag to the audit command allowing to filter the audit output by severity greater than or equal to the provided value which can be (info, low, moderate, high or critical).Test plan
Example:
This outputs all advisories ranked
high
andcritical
.By default without this new flag, the audit command will behave as it always did.