-
Notifications
You must be signed in to change notification settings - Fork 204
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
VCIO-next: Create improver to detect issues #1699
Comments
can I work on this issue? |
@saransh1307 you sure can, but this is a fairly complex issue for a start. |
Alright, @pombredanne, I'll focus on the suggested good first issues to build a solid understanding of the application. As I get more familiar with its structure and flow, I'll revisit this issue with a more informed perspective. |
@pombredanne this is the initial design I came up with, does this look good enough?
|
@keshav-space I would like to add to the list of issue_type values:
Thanks for working on this! |
We have sometimes issues and conflicts in the data we collect. For instance, we may have related advisories that contain different affected package version ranges. Or may disagree on the severity of a vulnerability or else. This is also something
For this we should create new improver to detect issues: it could detect and report discrepancies and conflicts in related advisories for a CVE, and flag these. That would later be input to curate these issues.
The text was updated successfully, but these errors were encountered: