omv-radarlisted

Variant-driven diffusion hunting for oh-my-vul. Use when the user has a confirmed or publicly disclosed vulnerability pattern and wants to find the same bug class in sibling packages, forks, or downstream consumers; also when they ask for watchlist maintenance, radar brief, or `/omv-radar`. Reads seeds from findings and advisories, applies variant playbooks, and hands screened candidates to omv-audit.
bx33661/oh-my-vul · ★ 4 · Code & Development · score 68

Install: claude install-skill bx33661/oh-my-vul

# omv-radar Turn one vulnerability pattern into many findings. Radar's job is diffusion: a deeply understood bug (even one you could not submit because it was already public) amortizes across every sibling package, fork, and downstream consumer that still has the same sink and the same missing guard. ## Invocation ```text /omv-radar variant <seed-id> # build a diffusion campaign from a seed /omv-radar brief # watchlist + active campaign status /omv-radar refresh [--dry-run] # watchlist maintenance only ``` ## Variant Workflow 1. Ingest the seed: read `.omv/findings/<seed-id>.yaml` (or a public advisory/fix-PR supplied by the user). Extract the seed fingerprint: sink shape, missing guard, and reachability precondition. All three are required — a sink without its precondition yields false positives. 2. Load `references/variant-playbooks.md` and classify the diffusion paths: sibling (same niche), fork/copied code, or downstream impact. State which paths apply to this seed and why. 3. Build the candidate list per path using the passive search mechanics in the playbook (registry keywords, code search, dependents graph, fix-commit mining). Names only, no auditing yet. 4. Quick-screen each candidate within the fetch budget (≤3 files): does the sink fingerprint exist, is the guard missing in the same way? Record candidates that pass with the evidence lines you saw. 5. Hand screened candidates to omv-audit as separate findings. Va