Awesome Reviewers

Verification · Testing

Fuzzing

Feeds coverage-guided random input to parsers and decoders to find crashes, panics and hangs.

Sub-techniques

  • Coverage-guided fuzzing V1022.001

    libFuzzer or AFL style harnesses per entry point.

  • Continuous fuzzing V1022.002

    Run fuzzers continuously (for example OSS-Fuzz) and file crashes as issues.

  • Corpus regression V1022.003

    Replay the saved corpus and crash cases in normal CI.

How to build it

  1. Write one harness per parser or decoder entry point.
  2. Seed the corpus with real inputs and commit it.
  3. Run short fuzz jobs on PRs and long ones on a schedule.

Signals in a repository

  • fuzz/ directories, fuzz_targets, or project.yaml for OSS-Fuzz.
  • CIFuzz or cargo fuzz steps in workflows.