Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed Plays.
Summary
syzkaller is an Apache-2.0 open-source command-line kernel fuzzer that uses unsupervised, coverage-guided testing to discover vulnerabilities across Linux and other operating-system kernels. It is self-hosted rather than a SaaSSaaSSoftware delivered over the internet and billed by subscription, hosted and operated by the vendor so the buyer skips installation and infrastructure management. service, aimed at kernel developers, vulnerability researchers, and security-testing teams who can build and run kernel targets. It sits in the kernel-fuzzing and appsec testing space, with documentation covering Linux, FreeBSD, Fuchsia, NetBSD, OpenBSD, Windows, and other systems. The project has issued 34 releases in the tracked period, with its latest release this week.
syzkaller is an unsupervised coverage-guided kernel fuzzer
+LLM backend and agent configurationNot checked yet · Date unknownManages model routing, context limits, multi-key distribution, and custom agent skills for automated analysis pipelines.11 releases · first seen Oct 2026▸
+Test environment configurationNot checked yet · Date unknownDetects host hardware capabilities, configures virtual machines and sandboxes, and verifies required system dependencies for execution.8 releases · first seen Oct 2026▸
+Kernel syscall descriptionsNot checked yet · Date unknownMaintains and updates system call definitions and kernel API descriptions across supported operating systems.7 releases · first seen Oct 2026▸
+Unsupervised kernel fuzzingNot checked yet · Date unknownProvides unsupervised, coverage-guided fuzzing capabilities for the Linux kernel.2 releases · 1 other source · first seen Oct 2026▸
+LoongArch64 guest supportNot checked yet · Date unknownExtends KVM fuzzing and tooling to loong64 guests, including KVM register state assertion via a dedicated pseudo-syscall, exit-test descriptions, and check-syzos.sh build toolchain support for the loongarch64 architecture.3 releases · first seen Nov 2026▸
+AI-assisted patch planningNot checked yet · Date unknownIntegrates reasoning models and planning agents into the code modification pipeline to generate patch strategies before edits.3 releases · first seen Oct 2026▸
+AI-assisted bisectionNot checked yet · Date unknownUses AI to identify the commits that introduced or fixed a kernel bug by analysing crash reports, reproducers, and optional root-cause analysis via bisect-cause and bisect-fix workflows in the aflow subsystem.2 releases · first seen Nov 2026▸
+AI security assessment bug routingNot checked yet · Date unknownAdds a route label to the dashboard that AI security assessments use to tag bugs with a routing destination, propagating the label to external bug reportings so downstream consumers receive it.2 releases · first seen Nov 2026▸
+Manager public HTTP endpointNot checked yet · Date unknownExposes the syz-manager dashboard at a configurable public-facing URL so that external dashboards and CI systems can link directly to it.1 release · 1 other source · first seen Oct 2026▸
+Dashboard subsystem configurationNot checked yet · Date unknownManages dashboard configuration entries and subsystem extraction rules for supported kernel versions, including enabling hardware subsystem profiles such as UFS.2 releases · first seen Oct 2026▸
+Differential kernel fuzzingNot checked yet · Date unknownOrchestrates fuzzing sessions that compare base and patched kernel binaries, skipping runs when the binaries are identical, via a reusable syz-cluster package.2 releases · first seen Oct 2026▸
+Cluster fuzz target scopingNot checked yet · Date unknownAllows syz-cluster fuzz targets to include static seeds and exclude specific paths via regexp filters, controlling the scope of fuzzing runs.2 releases · first seen Oct 2026▸
+RDMA network fuzzingNot checked yet · Date unknownConfigures RDMA hardware interfaces and network focus profiles to extend coverage to RDMA subsystems.2 releases · first seen Oct 2026▸
+Automated task executionNot checked yet · Date unknownOrchestrates parallel execution of fuzzing tasks, manages per-task logs, and persists executed seeds and results into a corpus database.2 releases · first seen Oct 2026▸
+vhost vsock fuzzingNot checked yet · Date unknownProvides executor helpers for setting up and sending data over vhost vsock interfaces to extend fuzzing coverage to that subsystem.1 release · first seen Nov 2026▸
+Multi-architecture target supportNot checked yet · Date unknownExtends syz-agent to support additional CPU architectures, including riscv64 and arm64 compat targets, with configurable target VM architecture selection.1 release · first seen Nov 2026▸
+Patch recipient managementNot checked yet · Date unknownSupports To/Cc recipient additions and removals during patch iteration within the aflow patching workflow, allowing reviewers to request email address changes alongside tag updates.1 release · first seen Nov 2026▸
+Per-bug embargo managementNot checked yet · Date unknownAllows the dashboard to assign and track individual embargo durations on a per-bug basis.1 release · first seen Nov 2026▸
+Impact and root cause analysis separationNot checked yet · Date unknownSeparates impact analysis from root cause analysis within the aflow package to allow each concern to be handled independently.1 release · first seen Nov 2026▸
+Lint enforcementNot checked yet · Date unknownEnforces code style rules on syzkaller source files, including requiring raw string literals for multi-line strings.1 release · first seen Oct 2026▸
+Source file linkificationNot checked yet · Date unknownConverts source file references in bug reports and other text into hyperlinks anchored to a specified kernel repository and commit, available in both HTML and Markdown output formats.1 release · first seen Oct 2026▸
+Infra-error retry limitingNot checked yet · Date unknownCaps the number of infrastructure-error retries in CollectRuns via a configurable MaxRetries field, returning a distinct error when the limit is exceeded.1 release · first seen Oct 2026▸
+AI-assisted bug report summarisationNot checked yet · Date unknownGenerates and includes AI-produced root cause analysis summaries in dashboard bug report emails.1 release · first seen Oct 2026▸
+Cluster boot testingNot checked yet · Date unknownProvides reusable smoke boot test logic as a standalone package for verifying kernel boot behaviour across syz-cluster components.1 release · first seen Oct 2026▸
+Cluster kernel build managementNot checked yet · Date unknownProvides shared kernel build logic as a reusable package for use across syz-cluster components.1 release · first seen Oct 2026▸
+Cluster symbol verificationNot checked yet · Date unknownChecks data symbols in both directions within syz-cluster to validate kernel patch correctness.1 release · first seen Oct 2026▸
+Stable backport recognitionNot checked yet · Date unknownRecognises AUTOSEL tags and version-range stable backport annotations when processing patch metadata in syz-cluster workflows.1 release · first seen Oct 2026▸
+Cluster network and protocol focus configurationsNot checked yet · Date unknownProvides preconfigured fuzzing focus modes in syz-cluster for specific protocol areas, including Bluetooth and USB, with expanded enabled syscall sets for each.1 release · first seen Oct 2026▸
+Corpus triageNot checked yet · Date unknownOptimizes patch testing workflows by automatically capping deflake runs and streamlining regression validation.1 release · first seen Oct 2026▸
+Memory safety executionNot checked yet · Date unknownControls executor-level memory safety flags and optimization settings across supported architectures.1 release · first seen Oct 2026▸
+Code searchNot checked yet · Date unknownEnables batched repository searches and per-file result counting for targeted code analysis.1 release · first seen Oct 2026▸
+Crash report parsingNot checked yet · Date unknownExtracts structured fault information and titles from kernel crash outputs for automated analysis.1 release · first seen Oct 2026▸
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for syzkaller, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail syzkaller puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
What syzkaller connects to, runs on and detects, read from its release notes and docs. So far: 5 new detections, 3 updated detections, 2 new supported platforms, 1 updated supported platform.
Nothing first seen in this window. That doesn't mean syzkaller shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-10
9
2026-11
2
How we count
Read from 13 of 22 release notes and docs updates we hold for syzkaller. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through syzkaller's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
Show
Coverage in all entries
22 entries
No entries match these filters.
November 202610
October 202612
Project health
Issue, contributor and maintainer activity in google/syzkaller, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed16%of issues opened, last 12 months
Median time to close8.1 daysfirst maintainer reply 20 hours
Open backlog522of 1,432 issues ever filed
Issues opened / month2 · 5communitymaintainers
Open backlog522
Contributors / monthnot measured
Commits / monthnot measured
Starsnot measured
Issue themes, last 12 months
bugs 36%
features 55%
other 9%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
We can only check tools that publish GitHub releases.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.