Botond Biro

What an agent can do with the cvewatch corpus

b070nd/cvewatch: Know which of your projects and environments are still exposed to which CVE, who owns the fix, and what happened so far

• Look up how cvewatch implements cli, cve, epss, with answers cited to file and line.
• Reuse a worked example: the commit “setup, status, catalog and project commands, MCP setup tools, S…” (8 files · Go).
• Answer from cvewatch's real Go source instead of memory (Security and vulnerabilities).

• How does cvewatch implement cli?
• What does app/src do in cvewatch?

Search the GitHub repository b070nd/cvewatch with XERJ (https://hub.xerj.org/corpus/b070nd--cvewatch).
Run these in a shell, in order, and check each result before the next:
1. xerj --help  (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh
2. git clone https://github.com/b070nd/cvewatch cvewatch && git -C cvewatch checkout 01f6df8dc838d42c98219e9eed536e83a42a4146
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./cvewatch --url http://127.0.0.1:9200 --prefix cvewatch --progress plain
5. xerj autoindex map --url http://127.0.0.1:9200
Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt
Licence: MIT. Keep the copyright notice and credit the authors.

corpus b070nd--cvewatch · Security and vulnerabilities
Related corpora: gosec-rules, golang-jwt, Lephiziel/findrail, NycolazSec/tcpcat
Code security audit with XERJ · Case study: reference coding for agents