-
Notifications
You must be signed in to change notification settings - Fork 21
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
[FEATURE] Ability to filter vulnerabilities based on score #155
Comments
Hi! First of all, thank you for opening your first issue. Elementary, we appreciate all feedback that helps us continue improving this plugin. As this is a community project we can't commit to official due dates for reviews and developing, but we're definitely committed to delivering services, integrations and plugins of top quality. So please be patient, we will review your issue and get back to you as soon as we can! Regards, |
Hi @sgilhooly!
When using
I like that idea!
You can submit your pull-request and we'll do our best to provide asistance 😄 Contributions from community are more than welcome 🎉 |
… to generate report without failing build
…eport without failing build (#158)
Hi @sgilhooly! Your contribution is now available on version 2.8.2: Please let us know if this works for you and thank you for taking the time to develop this new feature 😄 |
Thank you so much for considering it, reviewing it, and merging it! Looking forward to making good use of this plugin! |
What are you trying to do?
What feature or behavior is this required for?
How could we solve this issue? (Not knowing is okay!)
minimumScore
field to the OSS Audit extension which allows users to indicate what score a vulnerability must surpass before it is included in the results. This could work as part of the vulnerability filtering to exclude vulnerabilities which have a score lower than the configured value.Anything else?
cc @bhamail / @DarthHater / @guillermo-varela / @shaikhu
The text was updated successfully, but these errors were encountered: