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

sirupsen/logrus ↗

sirupsen/logrus AI coding statistics: 0.7%

of 151 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
0.7% 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
150
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%20
2026-031.7%59
2026-040%6
2026-050%3
2026-060%22
2026-080%41

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic10.7%

03Evidence

Inspect the matches

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

Matched commit samples

  • f42291d3 on GitHubfix: resolve deadlock when formatting triggers reentrant loggingClaude 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 window243
Merge commits removed−92
CI / dependency bots removed−0
Considered151

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
sirupsen/logrus
Default branch
master
Resolved HEAD
6d6a132bc03324d4ceb78e1b927f995d014cda20 ↗
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.

CohortGo · 132 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 62 of 194 ecosystem repositories excluded
Agent-commit share position32nd percentile

Midrank percentile; equal shares split the tied positions.

Repository
0.7%
Cohort median
2.8%
Share rank
89 / 132
0th50th100th

Percentile = (repositories below + half of 4 tied repositories) ÷ 132.

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 sirupsen/logrus

Scan another repository

Try