Pulse
2026-09-18-v3.0
Dataset
2026-10-27-catalog-ai-v2
Ruleset
b2e8889c66f7
Scanned
2026-10-27
Window
February–September 15, 2026
Catalog tracking observation. This repository is measured with the same fixed window and ruleset, but it is not part of the published benchmark or its aggregate claims.

MCP server to access Garmin data

Taxuspt/garmin_mcp ↗

Taxuspt/garmin_mcp AI coding statistics: 25.4%

of 114 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
25.4% agent · top contributor 24.1%11 contributors
org-wide

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

29
agent commits
85
other considered commits
11
agent contributors
24.1%
largest contributor

What shapes this result

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

Assisted or autonomous

29assisted
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.

Agent share by month

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-020%2
2026-030%8
2026-0525.8%31
2026-0633.3%27
2026-0746.2%13
2026-0825%4
2026-0917.2%29

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic2925.4%

Inspect the matches

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

Matched commit samples

  • 6c84f7cc on GitHubfix: keep the original error message when translating Garmin exceptionsClaude Code
  • 56e8ca2e on GitHubfix(training): carry VO2 max values forward so trend matches the Connect cClaude Code
  • b8ea7265 on GitHubfix(workouts): emit repeat groups so multi-set strength exercises keep theClaude Code

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 window156
Merge commits removed−31
CI / dependency bots removed−11
Considered114

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

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 Taxuspt/garmin_mcp

Scan another repository