gsd-tools VS cvelistV5

SQL won't prevent data errors any more than using JSON, you can have schema validation and the exact same data validation tooling, which we'd be more than happy to have, if you want to build this simply submit PR's against the tools repo: https://github.com/cloudsecurityalliance/gsd-tools

We, as an industry, didn't stop shipping bugs. (Small example: https://github.com/CVEProject/cvelistV5/releases)

And that thorough code review prevents bugs is, at best, a debatable assertion. See e.g. https://www.microsoft.com/en-us/research/publication/code-re...

It finds _some_ bugs. CI/CD, and a massive investment in automated testing has probably had the largest impact in moving software quality forward. (See e.g. "Accelerate", Forsgren, Humble & Kim)

Code review is an excellent tool to socialize knowledge and train up more junior engineers, but in terms of preventing bugs, it's low-value.

There seems to be new repository in a new JSON format: https://github.com/CVEProject/cvelistV5

Meanwhile, over here, I just stare at https://github.com/CVEProject/cvelistV5 and mumble "any reasonable dev, front of mind".

The issues I filed in the cvelistV5 repo are also unanswered, so I guess nobody gives a damn.

118955 entries don't even have an affected vendor/product software field, and neither with a valid version string and/or condition. They only contain plaintext descriptions and no version matching field either. Filed an issue here about it.