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

huiyadanli/RevokeMsgPatcher ↗

huiyadanli/RevokeMsgPatcher AI coding statistics: 11.1%

of 9 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
Too little recent activity to publish. Only 9 commits landed in this window, so the percentage is noisy. Repositories below 100 are excluded from the index for this reason.
11.1% 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
8
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-050%2
2026-070%2
2026-0820%5

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic111.1%

03Evidence

Inspect the matches

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

Matched commit samples

  • f1301c95 on GitHubfix: 支持微信 4.1.12.55 防撤回（特征码偏移改为通配，兼容 4.1.12.x） (#1226)Claude Code

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 window10
Merge commits removed−1
CI / dependency bots removed−0
Considered9

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
huiyadanli/RevokeMsgPatcher
Default branch
master
Resolved HEAD
8360fe2af70ef908dfe514eb78ca75129eacc5cc ↗
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.

CohortC# · 21 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 10 of 31 ecosystem repositories excluded
Comparison withheld for low activity

This observation does not meet the 100-commit publication threshold. The cohort definition and sample size remain visible so the omission is auditable.

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code 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 huiyadanli/RevokeMsgPatcher

Scan another repository

Try