google/honggfuzz

Security oriented software fuzzer. Supports evolutionary, feedback-driven fuzzing based on code coverage (SW and HW based)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 20th, 2026
Created on May 7th, 2015
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 539
Total Stargazers: 3,382 (+0)
Total Subscribers: 118 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 372 days
Stale 30+ days: 7
Stale 90+ days: 5

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

Honggfuzz is a security-oriented software fuzzer that performs evolutionary, feedback-driven fuzzing based on code coverage.

The tool addresses the problem of finding security vulnerabilities and bugs in software through automated testing. It works by generating and mutating test inputs, monitoring program execution for crashes and anomalies, and using code coverage feedback to guide the fuzzing process toward unexplored code paths. The fuzzer supports both software-based and hardware-based coverage instrumentation, allowing it to adapt to different target environments and optimization levels.

Honggfuzz suits security researchers, developers building safety-critical systems, and teams integrating fuzzing into their testing pipelines. It is particularly valuable for projects where discovering edge cases and potential vulnerabilities before deployment is essential. The tool's feedback-driven approach means it can discover deeper bugs than random fuzzing by intelligently exploring code paths that standard testing might miss. Teams should consider it when they need a fuzzer that can work across different architectures and can leverage hardware features for coverage tracking when available.

The project maintains active development with regular commits addressing bug fixes and feature improvements. The codebase shows consistent attention to security-related enhancements and performance optimizations. Pull requests receive timely review and integration, indicating engaged maintenance. The project demonstrates responsiveness to reported issues and maintains documentation alongside code changes.