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.

Home for "How To Scale Your Model", a short blog-style textbook about scaling LLMs on TPUs

jax-ml/scaling-book ↗

jax-ml/scaling-book AI coding statistics: 63.8%

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

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

30
agent commits
17
other considered commits
2
agent contributors
50%
largest contributor

What shapes this result

Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.

Assisted or autonomous

30assisted
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%2
2026-0350%2
2026-05100%13
2026-0633.3%9
2026-0764.7%17
2026-080%2
2026-09100%2

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic3063.8%

Inspect the matches

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

Matched commit samples

  • ac72f020 on GitHubAdd from-scratch LLaMA inference exercise to applied inference chapterClaude Code
  • 773f2dbe on GitHubFix hints and answers in JAX chapter worked problemsClaude Code
  • 37acb5ea on GitHubFix I_xy and J_xy panels in sharding-colored5.png (follow-up to #129)Claude Code

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 window48
Merge commits removed−1
CI / dependency bots removed−0
Considered47

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

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 jax-ml/scaling-book

Scan another repository