- Dataset
- 2026-10-27-catalog-ai-v2
- Ruleset
- b2e8889c66f7
- Scanned
- 2026-10-27
- Window
- February–September 15, 2026
Mirror only. Official repository is at https://git.zx2c4.com/wireguard-linux
01Result
WireGuard/wireguard-linux ↗WireGuard/wireguard-linux AI coding statistics: 0%
No signed agent commits found
No agent signatures were found in the last 54,186 considered commits. That is a real result, not a failure to measure.
It does not mean no AI was used here. A developer can use an agent and commit by hand without leaving a detectable git signature.
02Drivers
What shapes this result
Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.
Which agents
| Agent | Vendor | Commits | Share |
|---|---|---|---|
| Claude Code | Anthropic | 2 | 0% |
| Cursor Agent | Anysphere | 1 | 0% |
03Evidence
Inspect the matches
Public commit samples let you inspect the signatures behind the aggregate result.
Matched commit samples
d5dc1e69on GitHubinet: frags: strip GSO state from fragments before reassemblyClaude Codeabb5f367on GitHubsctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALLClaude Code00b91f3fon GitHubdrm/amd/display: Promote DC to 3.2.386Cursor Agent
04Method
What entered the denominator
The result begins with commit history, removes merges and routine automation, and reports literal agent signatures as a lower bound.
Exclusion ledger
| Commits in window | 59,178 |
| Merge commits removed | −4,992 |
| CI / dependency bots removed | −0 |
| Considered | 54,186 |
Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.
Continue exploring
Related coding-agent evidence
Run the same detector locally.
Deterministic signature matching; no code-style inference. Squash merges can remove trailers, so this result remains a measured floor.
npx qmmit-cli WireGuard/wireguard-linux