-
Notifications
You must be signed in to change notification settings - Fork 173
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
Surface all OSV schema fields on vulnerability details. #2081
Comments
I'm planning to work on this issue. |
Regarding per-range ecosystem/database_specific, if I understand it correctly, currently the both osv.dev/gcp/appengine/frontend3/src/templates/vulnerability.html Lines 133 to 156 in 0f4e0c2
Do we need to expose top level database_specific field (https://ossf.github.io/osv-schema/#database_specific-field)? |
Yes, we should expose the top level database specific field, though I'm not sure which entries have a top level database specific field. |
This change adds the following info to the vulnerability page: - purl: https://ossf.github.io/osv-schema/#affectedpackage-field - Severity: https://ossf.github.io/osv-schema/#severity-field - Credits: https://ossf.github.io/osv-schema/#credits-fields resolves #2081 Regarding the second items on the issue: per-range ecosystem/database_specific fields I left a [question](#2081 (comment)) on the issue.
Right now the vulnerabilities page is missing rendering of several fields that are part of the OSV JSON.
E.g.
The text was updated successfully, but these errors were encountered: