How trickest/cve works
CVE PoC is a public index of vulnerability records and links to proof-of-concept material. The main user workflow is to browse or search a CVE record and follow its PoC or reference links; the repository also documents an automated process for discovering, filtering, and publishing records. The year directories hold the catalog, while a small script converts those Markdown records into table data. The collection workflow is described in the README, but its implementation is not present in the supplied tree, so the graph does not infer internal calls between its stages.
Main entry points: CVE-1999-0001.md CVE records · generate_summary_json.py Summary generator
Components 14
CVE catalog
- CVE records
1999/CVE-1999-0001.md
PoC discovery
- Reference search
- GitHub search
- Merge and filter
- Markdown publishing
Catalog tools
- Summary generator
summary_html/generate_summary_json.py - Table JSON data
Other components
- Repository user
- cvelistV5
- GitHub PoC dataset
- ffuf
- False-positive blacklist
- shields.io
- Searchable HTML table
Connections 14
- Repository user → CVE records: browses
README.md - Repository user → Summary generator: runs
README.md - CVE records → Summary generator: reads
summary_html/generate_summary_json.py - Summary generator → Table JSON data: writes
summary_html/generate_summary_json.py - Table JSON data → Searchable HTML table: feeds
README.md - cvelistV5 → Reference search: provides CVEs
README.md - Reference search → ffuf: checks references
README.md - GitHub PoC dataset → GitHub search: provides PoC links
README.md - Reference search → Merge and filter: supplies results
README.md - GitHub search → Merge and filter: supplies results
README.md - Merge and filter → False-positive blacklist: filters with
README.md - Merge and filter → Markdown publishing: publishes records
README.md - Markdown publishing → CVE records: updates catalog
README.md - Markdown publishing → shields.io: generates badges
README.md