google/syzkaller

syzkaller is an unsupervised coverage-guided kernel fuzzer

View on GitHub ↗Jump to charts ↓Open shareable report →

google/syzkaller has 6k+ stars and 1k+ forks on GitHub, is written in Go, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 10th, 2026
Created on October 12th, 2015
Open Issues & Pull Requests: 635 (-3)
GitHub issues: Enabled
Number of forks: 1,460
Total Stargazers: 6,352 (+2)
Total Subscribers: 179 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.5 hours
Mean response time: 55.3 days
90th percentile: 76.2 days
Tracked items: 456

Maintainer activity

6 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 18% of issues opened in the past year have never received a reply. Only 16% of open issues come from outside the core team — the tracker reads mainly as internal planning. 73% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 49% of issues opened in the past year have been closed. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 283
New in 7 days: 3
Closed in 7 days: 0
Avg open age: 543 days
Stale 30+ days: 273
Stale 90+ days: 246

Recent activity

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

Top labels

  • enhancement (282)
  • bug (211)
  • AI patching (84)
  • syzbot user request (17)
  • syzbot ci (14)
  • research (8)
  • help wanted (7)
  • os:linux (7)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

syzkaller is a coverage-guided kernel fuzzer that automatically discovers bugs in operating system kernels through unsupervised fuzzing.

The tool addresses the challenge of finding security vulnerabilities and stability issues in kernel code by generating and executing randomized system call sequences. It uses coverage feedback to guide its fuzzing strategy, meaning it tracks which code paths have been exercised and prioritizes generating new inputs that reach unexplored areas of the kernel. This approach is more effective than random testing because it systematically explores the kernel's behavior space rather than blindly hammering it with arbitrary inputs.

Syzkaller is suited for kernel developers, security researchers, and maintainers who need to identify bugs before they reach production. It works across multiple operating systems and architectures, making it applicable to projects maintaining kernels or kernel-adjacent code. The tool is particularly valuable for continuous integration pipelines where automated fuzzing can run alongside traditional testing to catch edge cases and race conditions that manual testing might miss. Organizations with security-focused development practices benefit most from integrating syzkaller into their testing infrastructure.

The project maintains active development with regular commits addressing new kernel features and fuzzing strategies. The codebase receives ongoing refinement to improve crash detection and reporting accuracy. The tool continues to evolve with enhancements to its coverage instrumentation and input generation heuristics. Development activity shows sustained attention to expanding support for additional kernel subsystems and architectures.