Pulse
2026-09-18-v3.0
Dataset
2026-09-18-v3.0
Ruleset
b2e8889c66f7
Scanned
2026-09-16
Window
February–September 15, 2026
Local to this browser

01Result

zama-ai/fhevm ↗

zama-ai/fhevm AI coding statistics: 5.9%

of 555 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
5.9% agent · top contributor 30.3%16 contributors
org-wide

Adoption is broad. Many contributors are committing agent-authored work, which is what a real organisational rollout looks like.

33
agent commits
522
other considered commits
16
agent contributors
30.3%
largest contributor

02Drivers

What shapes this result

Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.

Assisted or autonomous

33assisted
0autonomous

Assisted — a developer’s identity authored the commit and the agent added itself as co-author. Autonomous — a bot identity authored the commit without a human identity attached. Across the whole index, 96% of agent commits are assisted.

Agent share by month

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-020%57
2026-031.5%65
2026-041.9%52
2026-052.7%74
2026-0612.5%64
2026-078.7%115
2026-088.3%60
2026-098.8%68

Peak month: 12.5%. Bars are scaled to that peak, not to 100%.

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic173.1%
Cursor AgentAnysphere142.5%
GitHub CopilotGitHub40.7%

03Evidence

Inspect the matches

Public commit samples let you inspect the signatures behind the aggregate result.

Matched commit samples

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 window555
Merge commits removed−0
CI / dependency bots removed−0
Considered555

Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.

05Provenance

Pinned to a source state

This observation names the repository state, release, and detector that produced it. Use these identifiers when reproducing or citing the result.

Dataset release
2026-09-18-v3.0
Scan date
2026-09-16
Ruleset
sha256:b2e8889c66f72c18a61839f0bf1a9f77b5481ba2def044dba33c797b2f2bdcae
Canonical repository
zama-ai/fhevm
Default branch
main
Resolved HEAD
4e2bd79e41b1adefa529af67efc9f9d127eb4f94 ↗
Resolved
2026-09-16
Measurement window
February–September 15, 2026
Download observation JSONDeterministic export · same values as this page

06Peer context

Position among comparable repositories

The cohort uses the same release and measurement window, then narrows to the repository’s ecosystem and removes low-activity observations.

CohortRust · 117 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 33 of 150 ecosystem repositories excluded
Agent-commit share position73rd percentile

Midrank percentile; equal shares split the tied positions.

Repository
5.9%
Cohort median
2%
Share rank
32 / 117
0th50th100th

Percentile = (repositories below + half of 1 tied repository) ÷ 117.

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code signatures →GitHub Copilot commitsBrowse repositories with detected GitHub Copilot signatures →Cursor Agent commitsBrowse repositories with detected Cursor Agent signatures →GitHub AI commit analyzerInspect another repository with the same evidence model →
Reproduce this observation

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 zama-ai/fhevm

Scan another repository

Try