fuzz-c-cppC/C++ fuzzing reference for libFuzzer, AFL++ and FuzzTest: harness formats, builds, runs, coverage, triage and regression commands. Not a starting point: use fuzz-harness or fuzz-campaign.
fuzz-campaignRuns a fuzzing campaign on C/C++, Java or JS/TS code, from threat model to hand-off. Use for "fuzz this project", "what should I fuzz?", "run this fuzzer for 4 hours", "analyze the long runs", "upstream my harnesses", "add fuzzing to CI", or to resume. Not for one harness or given crashes (fuzz-harn
fuzz-coverageMeasures a fuzz harness's source coverage, explains why attack-surface code stays uncovered, and applies the most valuable fix: seeds, dictionary, targeted inputs, harness or build change; also corpus merges. Use for "why is coverage stuck?" or "improve this fuzzer's coverage". Not for writing a new
fuzz-harnessWrites or extends a fuzz harness (fuzz test) for one entry point in the project's test style, builds its variants, adds seeds and a dictionary, and checks it with the harness gate. Use for "write a fuzz test for X", "build this with ASan and libFuzzer", or to check on or stop a fuzzing run. Not for
fuzz-javaJava fuzzing reference for Jazzer: @FuzzTest harnesses, Maven, Gradle, runs, JaCoCo coverage, detectors, hooks, triage and regression tests. Not a starting point: use fuzz-harness or fuzz-campaign.
fuzz-jsJS/TS fuzzing reference for Jazzer.js: CLI targets and Jest tests, setup, runs, coverage, detectors, hooks, triage and regression tests. Not a starting point: use fuzz-harness or fuzz-campaign.
fuzz-triageTriages fuzzer crashes (reproduce, group, minimize, root cause, verdict), fixes real bugs with a regression test, and drafts reports or advisories. Use for "triage these crashes", a crash file or sanitizer report (also from OSS-Fuzz or CI), "fix this crash" or "write an advisory for this bug". Not f
security-threat-modelBuilds a code-level threat model of a repository: attacker and deployment context, entry points that take untrusted data (sources), dangerous operations (sinks) and the paths between them, in .seclab/threat-model.md. Use for "threat model this repo", "what is the attack surface", or before fuzzing o