syzkaller — Engineering Performance
7 engineers all time · Jan 2025 – Sep 2026 · built 2026-09-08 · GitHub
Performance snapshot
Today's rolling 90-day reading for syzkaller, compared with the start of the series. Pick a window to move that comparison point.
Avg. perf / dev / mo
+10.3%
1.38 → 1.52 ETV
Active engineers
±0%
5.0 → 5.0
Features
−0.3pp
31.5% → 31.2%
vs. Google
0.59x
1.5x → 0.59x · −41% below
syzkaller vs. Google
Per-engineer ETV for syzkaller against Google as a whole. Both lines are 90-day rolling averages scaled to a 30-day month, so they share one axis and can be read against each other at any point. Pick a window to zoom the chart to it.
Performance Composition
Each month's output split by type of work: Features (new value), Maintenance (sustaining systems), Tests, Docs, and Fixes (rework). The yellow line is output per engineer, so when it rises each engineer is delivering more, whatever the team size did. Unit: Engineering Throughput Value (ETV).
Engineering capacity
Effective engineers behind syzkaller, against its pre-AI baseline. Each subject has its own: syzkaller's is 1.38 ETV / dev / mo, its first reading in April 2025. Per-engineer ETV divided by that gives a capacity multiple, and that multiple applied to the engineers active in the trailing 90 days turns it into engineer-equivalents. The line is the real headcount, so the gap between line and area is what the leverage is worth. Because each baseline is its own, every subject opens at 1.0x on its first day: multiples measure improvement and are not comparable between subjects.
Knowledge concentration
How dependent is this repo on a small number of engineers? Higher top-1 share = higher key-person risk.
Aleksandr Nogikh owns 46.8 % of commits.
Behind the numbers
Written summary of the work completed each month.
No monthly reports available yet.
Top engineers
Most impactful commits
Top 10 by ETV in the all-time window.
- 2.3ETVall: apply modernize linterDmitry Vyukov · 14befbc8 · 2026-06-01
- 2.1ETVall/mocks: updateTaras Madan · 49900278 · 2025-03-27
- 1.5ETVpkg/aflow: abstract LLM provider Decouple the aflow package from the google.golang.org/genai library to enable future integration with other LLM providers (e.g., Claude). Introduce a generic backend.Provider interface and corresponding types (Message, Part, GenerateConfig, etc.) in pkg/aflow/backend. Move the existing Gemini-specific logic into pkg/aflow/backend/gemini, which now implements this interface. Update the core aflow execution logic and agents to rely solely on the generic backend types. Finally, update syz-agent and tools/syz-aflow to explicitly initialize the Gemini provider and inject it into the workflow execution.Aleksandr Nogikh · fb92f11c · 2026-06-17
- 1.4ETVall: trivial for-loop range refactorings Fixes for "Use range over integer instead of traditional for loop" linter warnings that boil down to mechanical replacement. In certain cases untyped constants like 2e5 are converted to integer literals, because they are considered as floats and can't be used in range expressionsAlexander Potapenko · cf656f57 · 2026-04-17
- 1.3ETVpkg/aflow: add package for agentic workflowsDmitry Vyukov · 45d8f079 · 2026-01-02
- 1.2ETVall: use any instead of interface{} Any is the preferred over interface{} now in Go.Dmitry Vyukov · a83befa0 · 2025-12-19
- 1.2ETVdashboard/config/linux: add upstream-rust-kasan config Enable RUST as well as other Rust-related configs.Aleksandr Nogikh · b47f9e02 · 2025-05-15
- 1.1ETVsyz-cluster: report session results Provide an API to set up the reporting of finished sessions for which syz-cluster collected reportable findings. The actual sending of the results is to be done in a separate component that would: 1) Call Next() to get the next report to send. 2) Call Confirm() to confirm that the report has been sent. 3) Call Upstream() if the report has been moderated and needs to be sent to e.g. public mailing lists.Aleksandr Nogikh · f20e88b2 · 2025-02-13
- 1.1ETVdashboard/app: add support for AI workflows Support for: - polling for AI jobs - handling completion of AI jobs - submitting job trajectory logs - basic visualization for AI jobsDmitry Vyukov · 77200b36 · 2025-11-19
- 1.1ETVdashboard/config/linux: disable CONFIG_CGROUP_BPF It seems incredibly difficult to clean up the side effects of this kernel functionality. Keep it enabled only on a new config dedicated specifically for the snapshot-based instance. Closes #5956.Aleksandr Nogikh · 0ea0ca3f · 2025-07-16