google/clusterfuzz

Scalable fuzzing infrastructure.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 20 seconds ago
Added to GitGenius on September 12th, 2026
Created on January 29th, 2019
Open Issues & Pull Requests: 92 (+0)
GitHub issues: Enabled
Number of forks: 628
Total Stargazers: 5,600 (+0)
Total Subscribers: 114 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.9 hours
Mean response time: 51.6 days
90th percentile: 62.3 days
Tracked items: 166

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Work labelled "bug" is answered fastest, typically in under an hour, while "minor enhancement" waits about 26 hours. Only 10% of issues opened in the past year have been closed. Three people close 64% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 830 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 2

Top labels

  • stale (275)
  • autoclosed (268)
  • bug (29)
  • minor enhancement (22)
  • enhancement (19)
  • core feature (15)
  • documentation (7)
  • backlog (3)

Most active issues this week

Detailed Description

ClusterFuzz is a scalable fuzzing infrastructure that finds security and stability issues in software by running fuzz testing across distributed systems.

ClusterFuzz addresses the challenge of discovering vulnerabilities and crashes in software at scale. It works by orchestrating multiple coverage-guided fuzzing engines—libFuzzer, AFL, AFL++, and Honggfuzz—across a cluster of machines, coordinating their efforts through ensemble fuzzing and adaptive strategies. The system automatically deduplicates crashes to avoid redundant work, minimizes failing test cases to their simplest form, and performs regression finding through bisection to identify which code changes introduced bugs. It integrates with issue trackers like Monorail and Jira to automatically file, triage, and close bugs, reducing manual overhead in the vulnerability management workflow.

ClusterFuzz suits organizations that need continuous fuzzing at scale, from small projects to massive deployments running on tens of thousands of machines. It works well for projects already committed to fuzzing as part of their development process and for those managing multiple codebases that benefit from centralized fuzzing infrastructure. The tool provides a web interface for crash management and viewing statistics about fuzzer performance and crash rates. For teams wanting a lighter-weight alternative that integrates into CI/CD pipelines rather than requiring dedicated infrastructure, the project documentation mentions ClusterFuzzLite as an option.

The project maintains active issue tracking where developers can ask questions and request features. The team uses a dedicated announcement channel to communicate updates about the tool. Development activity shows consistent engagement with the codebase, with regular updates addressing both new capabilities and maintenance of the fuzzing infrastructure.