- Dataset
- 2026-10-27-catalog-ai-v2
- Ruleset
- b2e8889c66f7
- Scanned
- 2026-10-27
- Window
- February–September 15, 2026
Production-grade Turborepo template for Next.js apps.
01Result
vercel/next-forge ↗vercel/next-forge AI coding statistics: 36.4%
One person is driving this. The headline number reflects a single contributor's workflow, not a project-wide shift.
02Drivers
What shapes this result
Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.
Assisted or autonomous
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
| Month | Agent share | Considered commits |
|---|---|---|
| 2026-03 | 38.1% | 21 |
| 2026-05 | 0% | 1 |
Peak month: 38.1%. Bars are scaled to that peak, not to 100%.
Which agents
| Agent | Vendor | Commits | Share |
|---|---|---|---|
| Claude Code | Anthropic | 8 | 36.4% |
03Evidence
Inspect the matches
Public commit samples let you inspect the signatures behind the aggregate result.
Matched commit samples
b3966168on GitHubFeat/trunk integration (#735)Claude Codeeb4a370aon GitHubAdd c15t addon (#728)Claude Code71979c3fon GitHubRemove sed step, setup-node handles OIDC exchangeClaude Code
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 | 23 |
| Merge commits removed | −0 |
| CI / dependency bots removed | −1 |
| Considered | 22 |
Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.
Continue exploring
Related coding-agent evidence
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 vercel/next-forge