Cve/researcher
Daily CVE research pipeline — queries NVD, GitHub Advisory DB, and CISA KEV for HIGH/CRITICAL vulnerabilities, classifies them by real-world impact (supply-chain, infrastructure, open-source library, vendor product), and scores each for actionability to identify which CVEs warrant a dedicated swamp scanner extension.
Methods
research— query all three CVE sources, filter by lookback window and severity, deduplicate, classify, score, and persist results with state tracking for idempotent alerting
Report
Generates a markdown report grouped by actionability:
- Extension Candidates (score 7+) — detailed with scoring breakdown
- Monitor (score 4–6) — worth tracking
- Patch Only (<4) — summary counts by classification
Workflow
Bundled cve-research workflow runs the research method and posts a
rich Discord embed summary via @keeb/discord. Designed to run daily
in a GitHub Action on a cron schedule.
Secrets
Both NVD_API_KEY and DISCORD_WEBHOOK_URL can be supplied as
vault-backed global arguments (nvdApiKey, webhookUrl) via
${{ vault.get('<vault>', '<key>') }} expressions, or as plain
environment variables as a fallback.
Resources
Daily CVE research — queries NVD, GitHub Advisory DB, and CISA KEV for new HIGH/CRITICAL vulnerabilities
Markdown CVE research report with real-world classification and actionability scoring
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented0/1missing
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Docs keep secrets in a vault0/1missing
- files/README.md--Line 162 uses `swamp vault set` (the command is `swamp vault put`), which swamp does not resolve as a vault reference. Keep secrets in a vault: store them with `swamp vault put <vault> <key>`, which prompts for the value, and reference them as `${{ vault.get(<vault>, <key>) }}`.
- files/README.md--Line 163 uses `swamp vault set` (the command is `swamp vault put`), which swamp does not resolve as a vault reference. Keep secrets in a vault: store them with `swamp vault put <vault> <key>`, which prompts for the value, and reference them as `${{ vault.get(<vault>, <key>) }}`.
Fix or accept each secret-unsafe-docs warning: the README, the manifest description and describe strings should store secrets with `swamp vault put <vault> <key>` (it prompts for the value) and pass them as `${{ vault.get(<vault>, <key>) }}`.
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License2/2earned
- Verified public repository2/2earned