Systemic issue with OSV JSON Schema compliance
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 544
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 45
Description
Hi,
By the looks of it, there's a systemic issue with how OSV records are being generated (invalid schema_version field).
OSV.dev would like to start validating OSV records imported both against the JSON Schema and (separately) the Properties of a High Quality OSV Record so it would be good to address this issue in the short term.
We'll be in touch separately about any other problems we identify with your records.
/cc @hogo6002
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked gist and the OSV schema's schema_version field, then trace how this repository's OSV records are generated. Validate the resulting records against the JSON Schema and confirm that the schema_version field complies with the documented format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- database, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100