-
Notifications
You must be signed in to change notification settings - Fork 169
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] When ingesting VEX documents add NoVuln node if package is not affected #1015
Labels
enhancement
New feature or request
Comments
@dejanb I think i recall this conversation being about products that did not have a vulnerability. Is that accurate? or am i recalling wrong? |
@lumjjb I think that's tracked with #1016. This one is to specifically track adding `NoVuln' nodes where appropriate I might as well recalling it wrong, so please feel free to add more issues/context to this. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
During development of VEX CSAF support we ignored packages described as not affected by the vulnerability. It was left to be handled in separate issue.
Describe the solution you'd like
If package is not affected, add
NoVuln
node.The text was updated successfully, but these errors were encountered: