Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bug(ghsa): add support of last_known_affected_version_range #391

Closed
DmitriyLewen opened this issue Mar 11, 2024 · 0 comments · Fixed by #392
Closed

bug(ghsa): add support of last_known_affected_version_range #391

DmitriyLewen opened this issue Mar 11, 2024 · 0 comments · Fixed by #392

Comments

@DmitriyLewen
Copy link
Contributor

DmitriyLewen commented Mar 11, 2024 •
edited
Loading

Description

ghsa uses last_known_affected_version_range (e.g. https://github.com/github/advisory-database/blob/88a23ee5cad40396bcd47a136bd21753b96e86da/advisories/github-reviewed/2023/04/GHSA-32qq-m9fh-f74w/GHSA-32qq-m9fh-f74w.json#L34).
We need to add support for this field.

UPD:
Use cases of last_known_affected_version_range field -github/advisory-database#470 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(ghsa): add support of last_known_affected_version_range field DmitriyLewen/trivy-db
1 participant
@DmitriyLewen