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.

Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q

01Result

litmuschaos/litmus ↗

litmuschaos/litmus AI coding statistics: 3.3%

of 91 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
Too little recent activity to publish. Only 91 commits landed in this window, so the percentage is noisy. Repositories below 100 are excluded from the index for this reason.
3.3% agent · top contributor 66.7%2 contributors
individual

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

3
agent commits
88
other considered commits
2
agent contributors
66.7%
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

3assisted
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-0214.3%14
2026-030%11
2026-040%9
2026-050%15
2026-060%20
2026-077.7%13
2026-080%9

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

Which agents

AgentVendorCommitsShare
GitHub CopilotGitHub22.2%
Cursor AgentAnysphere11.1%

03Evidence

Inspect the matches

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

Matched commit samples

  • 23675c3a on GitHubfeat: add support for targeting Jobs in chaos experiments (#5433)GitHub Copilot
  • 232163aa on GitHubfix: return 503 when database is down ensuring proper probe detection (#54GitHub Copilot
  • 8a5a9e27 on GitHubdocs(adopters): add Motorola Solutions and list Canonical (#5575)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 window97
Merge commits removed−0
CI / dependency bots removed−6
Considered91

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

Continue exploring

GitHub Copilot commitsBrowse repositories with detected GitHub Copilot signatures →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 litmuschaos/litmus

Scan another repository

Try