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.

Machine learning metrics for distributed, scalable PyTorch applications.

Lightning-AI/torchmetrics ↗

Lightning-AI/torchmetrics AI coding statistics: 19.4%

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

A small group is using agents. Adoption has spread beyond one person but is not project-wide.

6
agent commits
25
other considered commits
5
agent contributors
33.3%
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

6assisted
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%3
2026-0316.7%6
2026-040%3
2026-050%4
2026-060%1
2026-0766.7%3
2026-080%3
2026-0937.5%8

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic39.7%
GitHub CopilotGitHub39.7%

Inspect the matches

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

Matched commit samples

  • 093de1e3 on GitHubFix PESQ aborting a whole batch on one unscorable sample (#3455)Claude Code
  • 0ca54b2b on GitHubfix(docs): ignore NIST link causing intermittent linkcheck 504 (#3431)Claude Code
  • dd8fa06d on GitHubFix malformed LaTeX in CLIPScore and HausdorffDistance docstring math (#34Claude Code
  • d6c8aa5b on GitHubFix chrF dropping the reference n-grams of a zero-scoring sentence (#3481)GitHub Copilot
  • 6b0d4c1a on GitHubfix(clip_score): unwrap dataclass output from get_image/text_features (#34GitHub Copilot
  • 32f3e017 on GitHubFix race condition in `_safe_divide` by creating tensor directly on deviceGitHub Copilot

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 window47
Merge commits removed−0
CI / dependency bots removed−16
Considered31

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 Lightning-AI/torchmetrics

Scan another repository