Some OSV json files containing GitHub advisories available via www.googleapis.com seem to include the patched versions in the affected versions list. I have included two examples containing this issue below:
The references list in the JSON files do contain urls linking to the patched releases, so the information to correctly parse the fixed versions was avaiable. Is this an issue with OSV, or with GHSA? Or is the information avaiable via googleapis not up to date?
The files available via https://api.osv.dev/ do denote the right fixed versions.
Thank you in advance,
Tom
Some OSV json files containing GitHub advisories available via
www.googleapis.comseem to include the patched versions in the affected versions list. I have included two examples containing this issue below:OSV JSON file from googleapis
Patched versions 19.2.16, 20.3.14, and 21.0.1 are included in the affected versions list.
OSV JSON file from googleapis.
Patched versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2 are included in the affected versions list
The references list in the JSON files do contain urls linking to the patched releases, so the information to correctly parse the fixed versions was avaiable. Is this an issue with OSV, or with GHSA? Or is the information avaiable via
googleapisnot up to date?The files available via
https://api.osv.dev/do denote the right fixed versions.Thank you in advance,
Tom