-
Notifications
You must be signed in to change notification settings - Fork 220
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
Include affected platforms in stored vulnerability data #149
Comments
This will be fixed, once we use JSONField for storing a purl's qualifiers right? |
Coincidently, I was trying to do exactly that today, had the debian importer running for awhile ,which didn't finish due to powercut :( . I will try that once again. |
Not working, it is storing the qualifiers as a single json string ie |
Can be fixed easily in https://github.com/package-url/packageurl-python/blob/00b7df61173be3c19eb65ce166271aed0e9ae00c/src/packageurl/contrib/django_models.py#L123 by setting |
Some security issues only affect certain platform (as in operating systems, Linux distributions, etc.) The data model should include this information and allow querying for it to avoid false positives. The natural way to include this on the query side is with a platform qualifier on the package URL.
Here is an example of a vulnerability in a Rust crate that only affects Windows: https://github.com/RustSec/advisory-db/blob/master/crates/hyper/RUSTSEC-2016-0002.toml
The text was updated successfully, but these errors were encountered: