Andrew Pollock

@masterismail it looks like there's one last lint finding to address, you're close!

Yes, it's very much being actively worked on. I will look at defining and sharing some milestones, help is always welcome :-) Everything's currently in a proof-of-concept stage, as I...

This issue is overdue for a status update. Work has been progressing well, and the most recent conversion runs are yielding the following results from the 2022 NVD CVE data...

Another overdue status update We're close (targeting early October) to going live with the data currently available. CVEs from 2023-2016 are being processed. From the 2023 NVD CVE data set:...

Early access update for followers of this issue 👋 We've soft-launched this into OSV.dev production overnight, and we now have 31,889 NVD CVE-based records from 2023-2016 in OSV.dev, e.g: -...

Hi @slonka I can advise as of https://github.com/google/osv-scanner/releases/tag/v1.4.3, which went out a few hours ago, the functionality is now fully available in OSV-Scanner directly, as well as the REST API.

> Despite [CVE-2016-8616](https://curl.se/docs/CVE-2016-8616.json) existing in datastore, it is not visible on the website. So I've got a better understanding of what's necessary for future reference: Some of these Curl records...

@mustafaazad03 go for it!

Happy New Year @mustafaazad03 I thought I'd check in and see how you're going with this?

> is adding RedHat datasource on your roadmap? We're largely dependent on Red Hat to provide the data in the OSV format, conversations are ongoing... /cc @mprpic