mirror of
https://github.com/0xMarcio/cve.git
synced 2026-10-27 16:51:03 +00:00
0xMarcio
164b2a6fad
The first one never worked. It selected CVE-2026-75604, an id lifted from a trending repository name without checking the CVE was in the index, and it is not, so the command downloaded 48 MB to print nothing. The repo_meta example was worse: it returned null every time, because those keys are lowercased and the example was not. Every command in the README has now been run against the deployed files, and the block is regenerated from the same source, so what is printed is what was tested. The examples also answer questions worth asking rather than restating the schema: what the index knows about one CVE across all four sources, how bad it is and how likely it is to be used, and what CISA says is being exploited that also has a PoC here, ranked by exploitation probability. The endpoint table gains the two new files and notes the size of the big one and the key casing that caused this. A sources table replaces guessing where any of it came from.