TESTING / trailofbits
OSS-Fuzz Integration
Prepare an open-source project for continuous fuzzing and reproduce its harnesses locally.
“Enrolls a project in OSS-Fuzz, Google's free continuous fuzzing service for open source, and drives it locally. Covers project.yaml, Dockerfile and build.sh setup, the helper”
01 / THE REASONING
Why this made the selection.
- The skill separates a local helper.py run from public enrollment, which it describes as selective.
- A private project is told to host its own instance or stay on local helper runs, not to expect public OSS-Fuzz.
- The definition provides the three-file integration contract, local helper workflow and engine linkage through LIB_FUZZING_ENGINE.
- Create project.yaml, Dockerfile and build.sh for a proposed integration
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- plugins/testing-handbook-skills/skills/ossfuzz/SKILL.md
- LICENSE
- README.md
Our findings
- Local runs need a clone of google/oss-fuzz and Docker through infra/helper.py. That is network and a local daemon, not a scan this skill performs by itself.
- Public enrollment is not automatic. The file says only some projects are accepted and private projects are not eligible for the public service.
- It does not replace a small local fuzz target that does not need the OSS-Fuzz images, which it lists as a reason not to use the platform.
- The definition provides the three-file integration contract, local helper workflow and engine linkage through LIB_FUZZING_ENGINE.
Not established by this review
- The resource was not executed and its tools were not called.
- helper.py was not run and Docker was not started.
- No skill execution, authenticated service operation, or outcome benchmark was performed.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add trailofbits/skills/plugins/testing-handbook-skills/skills/ossfuzz Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/trailofbits/skills/tree/8e54050ae63c2f62224c35b1616efe71865b4777/plugins/testing-handbook-skills/skills/ossfuzz - Install the pinned skill directory interactively, retaining its bundled references and scripts.
- Check current acceptance guidance and maintainer contacts before preparing a public submission.
- Use the checked-out helper help, build the project image and fuzzers locally, and retain sanitizer/corpus settings when reproducing a crash.
Before you start
- Docker and a supported build host
- Python/uv and an OSS-Fuzz checkout
- Authorized source and any required corpus access
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Pinned skill definition ↗Checked
https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/plugins/testing-handbook-skills/skills/ossfuzz/SKILL.md
Supports: summary, whySelected, bestFor, limitations, install, access, review
https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/README.md
Supports: install
- CC-BY-SA-4.0 licence ↗Checked
https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/LICENSE
Supports: license
https://google.github.io/oss-fuzz/getting-started/accepting-new-projects/
Supports: limitations, install