ossfuzz

Run OSS-Fuzz harnesses locally and generate coverage reports.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill ossfuzz-ayehiaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ossfuzz
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/ossfuzz
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill ossfuzz-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OSS-Fuzz helps you continuously fuzz open-source software to uncover crashes, security bugs, and coverage gaps faster than one-off local runs.

Core Features & Use Cases

  • Distributed continuous fuzzing infrastructure: use OSS-Fuzz’s hosted pipeline instead of building and operating fuzzing servers yourself.
  • Local harness execution and coverage reports: run individual harnesses locally and generate coverage output for analysis.
  • Enrollment-ready project setup: prepare project.yaml, Dockerfile, and build.sh to integrate with OSS-Fuzz’s build and harness workflow (or validate your setup before enrolling).

Use case example: you have an existing fuzz harness and want to reproduce an OSS-Fuzz crash locally and confirm whether the fix improves coverage using the same helper workflow.

Quick Start

Run a single harness locally by executing: python3 infra/helper.py run_fuzzer <project-name> <harness-name>

Frequently Asked Questions about ossfuzz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up continuous fuzzing for an open-source project?

You can run a single fuzz harness locally by executing the OSS-Fuzz helper CLI: python3 infra/helper.py run_fuzzer <project-name> <harness-name>. This builds the project images and executes the specified harness within a containerized environment.

How do I reproduce an OSS-Fuzz crash locally?

You can generate a coverage report by utilizing the OSS-Fuzz coverage and coverage-sanitizer workflows. This analyzes your fuzz harness execution output to identify uncovered code paths and coverage gaps in your project.

Do I need Docker to run OSS-Fuzz helper workflows?

OSS-Fuzz leverages distributed continuous fuzzing infrastructure, which provides a hosted pipeline for uncovering crashes and security bugs. This approach eliminates the need to build and operate your own fuzzing servers, offering faster and more scalable vulnerability detection.

Can I use libfuzzer with OSS-Fuzz continuous fuzzing infrastructure?

Yes, libfuzzer is supported as a fuzzing engine within the OSS-Fuzz continuous fuzzing infrastructure. You can integrate it through your project configuration to execute harnesses and analyze coverage across supported sanitizers.