Get the contents published at osv.dev #9
Description
That's the goal. The first step was to register the OSEC to opam in the osv-schema -- ossf/osv-schema#473
The next steps are documented in google/osv.dev#4581, and are waiting at the moment for "add the opam ecosystem to their python code" (PR google/osv.dev#4582)
This is merged now, we can continue with the following steps:
- Create a PR to start importing the records you are publishing into our test instance of OSV.dev and validate everything is working as intended there. -- done at feat: Add opam source (https://github.com/ocaml/security-advisories) to testing google/osv.dev#4632
- Once test instance source is merged and looks good, Create a PR to start importing the records you are publishing into our production environment -- see feat: Add opam source (https://github.com/ocaml/security-advisories) to prod google/osv.dev#4651