Verification · Testing · Fuzzing
Continuous fuzzing
Run fuzzers continuously (for example OSS-Fuzz) and file crashes as issues.
How to build it
- Enrol the project in a hosted continuous fuzzing service, such as OSS-Fuzz.
- Configure the service build script so it builds every harness.
- Set each crash to open an issue in the project tracker.
Signals in a repository
- A project.yaml or build script for OSS-Fuzz in the repository.
- A CIFuzz step or scheduled workflow that runs fuzzers for a long time.
- Issues labelled as fuzzing crashes that the service filed.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.