The new tooling in tools uses JSON-formatted GHSA data from https://osv-vulnerabilities.storage.googleapis.com/Maven/all.zip. However, this file appears to be missing unreviewed GHSAs such as GHSA-g7jw-7782-jjv9 (corresponding to CVE-2016-0779, which vul4j's CVE-2015-8581 ( = VUL4J-37) is marked as a dupe of).
Some googling found me this page describing a matching JSON schema, which says that GHSA data in this format is available from https://api.osv.dev/v1/vulns/<ID> (@alexjordan could you confirm that this schema is the right one and this API is what all.zip is generated from?). But although curl https://api.osv.dev/v1/vulns/GHSA-g74w-93cp-5p3p works as expected and matches the GHSA-g74w-93cp-5p3p inside all.zip (modulo whitespace), curl https://api.osv.dev/v1/vulns/GHSA-g7jw-7782-jjv9 only gives {"code":5,"message":"Bug not found."}.
The new tooling in
toolsuses JSON-formatted GHSA data from https://osv-vulnerabilities.storage.googleapis.com/Maven/all.zip. However, this file appears to be missing unreviewed GHSAs such as GHSA-g7jw-7782-jjv9 (corresponding toCVE-2016-0779, which vul4j'sCVE-2015-8581( =VUL4J-37) is marked as a dupe of).Some googling found me this page describing a matching JSON schema, which says that GHSA data in this format is available from
https://api.osv.dev/v1/vulns/<ID>(@alexjordan could you confirm that this schema is the right one and this API is whatall.zipis generated from?). But althoughcurl https://api.osv.dev/v1/vulns/GHSA-g74w-93cp-5p3pworks as expected and matches theGHSA-g74w-93cp-5p3pinsideall.zip(modulo whitespace),curl https://api.osv.dev/v1/vulns/GHSA-g7jw-7782-jjv9only gives{"code":5,"message":"Bug not found."}.