cve-dashboard: package-cve events #149
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This event collects data about detected CVEs that our cve-dashboard has previously received and inspected to open/close CVE issues affecting pairs <package/CVE-ID>.
Initially I thought about creating two types of Events one for detection and another when resolving a CVE for a package. However I didn't see much of a different between the list of involved attr per event type.
I've added fields such as Reason (to add any details when closing an issue) or Type to filter them by
detectionorresolution.This event would be used by many other future services which will be decomposed on separate services but are now part of the cve-dashboard service.