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.

A tool that allows you to create vulnerable instrumented local or cloud environments to simulate attacks against and collect the data into Splunk

01Result

splunk/attack_range ↗

splunk/attack_range AI coding statistics: 8.3%

of 36 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate

Too little recent activity to publish. Only 36 commits landed in this window, so the percentage is noisy. Repositories below 100 are excluded from the index for this reason.

8.3% 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.

agent commits

other considered commits

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

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

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

Which agents

Agent	Vendor	Commits	Share
Cursor Agent	Anysphere	3	8.3%

03Evidence

Inspect the matches

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

Matched commit samples

fde5ade5 on GitHubEnsure E2E AWS cleanup runs when the test step times out.Cursor Agent
96dd6c6f on GitHubAdd post-build apply-role support for local Ansible roles.Cursor Agent
7f0b5dea on GitHubAdd ATTACK_RANGE_LOCAL_ROLES for local Ansible role development.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 window	55
Merge commits removed	−18
CI / dependency bots removed	−1
Considered	36

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 →Python AI coding statisticsCompare evidence across Python 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 splunk/attack_range

Scan another repository

Try

Agent-attributed commit share by month
Month	Agent share	Considered commits
2026-02	0%	26
2026-06	37.5%	8
2026-08	0%	2