-
Notifications
You must be signed in to change notification settings - Fork 205
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
Importers without a vulnerable package list #449
Comments
Are you sure this is deprecating this ? |
See #140 (comment) |
As an example when I look at https://github.com/mozilla/foundation-security-advisories/blob/c5f33af98294e441311fa9ec904001b09934af73/announce/2021/mfsa2021-27.yml#L4 we have a fixed package. We should support these with no impacted packages alright too. |
#436 deprecates the concept of
fixed_package
and now only the vulnerable packages are entered into the database. Many data sources do not provide with a list of vulnerable packages and only provide a fixed version.Currently affected importers:
Future affected importers:
We cannot simply ignore these data sources. One approach would be to flag all the versions before the provided fixed version as vulnerable and enter those in the database. The meaning of only a fixed version could further be clarified at the data source's end.
This needs to be further discussed.
The text was updated successfully, but these errors were encountered: