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

Raphire/Win11Debloat ↗

Raphire/Win11Debloat AI coding statistics: 0.4%

of 225 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
0.4% agent · top contributor 100%1 contributor
individual

One person is driving this. The headline number reflects a single contributor's workflow, not a project-wide shift.

1
agent commits
224
other considered commits
1
agent contributors
100%
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

1assisted
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%56
2026-030%41
2026-040%26
2026-056.7%15
2026-060%39
2026-070%27
2026-080%20
2026-090%1

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

Which agents

AgentVendorCommitsShare
GitHub CopilotGitHub10.4%

03Evidence

Inspect the matches

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

Matched commit samples

  • 24a6f1bc on GitHubFix capture and restore of signed dword/qword registry valuesGitHub Copilot

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 window231
Merge commits removed−6
CI / dependency bots removed−0
Considered225

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
Raphire/Win11Debloat
Default branch
master
Resolved HEAD
32024662f3c602442e7af82bbf52c89143b31aeb ↗
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.

CohortPowerShell · 4 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 2 of 6 ecosystem repositories excluded
Comparison withheld for a small cohort

Only 4 eligible repositories remain; qmmit requires at least 10 before showing a percentile. The cohort definition and sample size remain visible so the omission is auditable.

Continue exploring

GitHub Copilot commitsBrowse repositories with detected GitHub Copilot 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 Raphire/Win11Debloat

Scan another repository

Try