Refactor severity score model and fix incorrect suse scores

aboutcode-org / vulnerablecode

A free and open vulnerabilities database and the packages they impact. And the tools to aggregate and correlate these vulnerabilities. Sponsored by NLnet https://nlnet.nl/project/vulnerabilitydatabase/ for https://www.aboutcode.org/ Chat at https://gitter.im/aboutcode-org/vulnerablecode Docs at https://vulnerablecode.readthedocs.org/

Apache License 2.0

543 stars 201 forks source link

Add a severities field to both AffectedByPackageRelatedVulnerability and Vulnerability.
Add url field to VulnerabilitySeverity and remove reference relationship.
Create migrations to remove corrupted suse scores and enable reprocessing of old suse advisories on the next import cycle.
Populate the new url field in VulnerabilitySeverity using references, set the severity-vulnerablity relationship from the old model.
Update UI, API, APIv2, importer/pipeline, and export command to use the new model.
Use new severity model for risk calculation
Use optimized queryset in risk pipeline

Resolves https://github.com/aboutcode-org/vulnerablecode/issues/1597

aboutcode-org / vulnerablecode

Refactor severity score model and fix incorrect suse scores #1636