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.

kro | Kube Resource Orchestrator

01Result

kubernetes-sigs/kro ↗

kubernetes-sigs/kro AI coding statistics: 0.4%

of 224 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
223
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.

Agent share by month

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-020%29
2026-030.7%140
2026-040%35
2026-050%15
2026-060%3
2026-080%1
2026-090%1

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

Which agents

AgentVendorCommitsShare
Cursor AgentAnysphere10.4%

03Evidence

Inspect the matches

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

Matched commit samples

  • ad431c5d on GitHubfix: do not count requeue signals as handler errors in dynamic_controller_Cursor Agent

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 window343
Merge commits removed−8
CI / dependency bots removed−111
Considered224

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

Continue exploring

Cursor Agent commitsBrowse repositories with detected Cursor Agent signatures →Go AI coding statisticsCompare evidence across Go repositories →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 kubernetes-sigs/kro

Scan another repository

Try