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.

Hands on exercises with real-life examples to study and practice Go concurrency patterns. Test-cases are provided to verify your answers.

01Result

loong/go-concurrency-exercises ↗

loong/go-concurrency-exercises AI coding statistics: 100%

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

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

100% 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

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.

Which agents

Agent	Vendor	Commits	Share
Cursor Agent	Anysphere	1	100%

03Evidence

Inspect the matches

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

Matched commit samples

110b98d0 on GitHubMake the workshop discoverable and usable by coding agentsCursor 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	2
Merge commits removed	−1
CI / dependency bots removed	−0
Considered	1

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 loong/go-concurrency-exercises

Scan another repository

Try