Dataset: 2026-09-18-v3.0
Ruleset: b2e8889c66f7
Scanned: 2026-09-16
Window: February–September 15, 2026

Local to this browser

01Result

plotly/plotly.js ↗

plotly/plotly.js AI coding statistics: 0.7%

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

0.7% agent · top contributor 42.9%4 contributors

team

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

7

agent commits

967

other considered commits

4

agent contributors

42.9%

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

7assisted

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. Across the whole index, 96% of agent commits are assisted.

Agent share by month

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

Which agents

Agent	Vendor	Commits	Share
Claude Code	Anthropic	6	0.6%
Cursor Agent	Anysphere	1	0.1%

03Evidence

Inspect the matches

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

Matched commit samples

7011939c on GitHubAddress review feedback: extract domain-clamping helpersClaude Code
4d427c71 on GitHubAdd draftlog entry for PR #7908Claude Code
b121bc92 on GitHubClamp colorbar axis domain so it can never invertClaude Code
4d9f656d on GitHubReuse scatter selectPoints for quiver instead of duplicating selection logCursor 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	1,179
Merge commits removed	−197
CI / dependency bots removed	−8
Considered	974

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

05Provenance

Pinned to a source state

This observation names the repository state, release, and detector that produced it. Use these identifiers when reproducing or citing the result.

Dataset release: 2026-09-18-v3.0
Scan date: 2026-09-16
Ruleset: sha256:b2e8889c66f72c18a61839f0bf1a9f77b5481ba2def044dba33c797b2f2bdcae
Canonical repository: plotly/plotly.js
Default branch: main
Resolved HEAD: 7f857ee5738b2f8da0695fb0297b32080ede8b41 ↗
Resolved: 2026-09-16
Measurement window: February–September 15, 2026

Download observation JSONDeterministic export · same values as this page

06Peer context

Position among comparable repositories

The cohort uses the same release and measurement window, then narrows to the repository’s ecosystem and removes low-activity observations.

CohortJS/TS · 376 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 194 of 570 ecosystem repositories excluded

Agent-commit share position21st percentile

Midrank percentile; equal shares split the tied positions.

Repository: 0.7%
Cohort median: 5.4%
Share rank: 295 / 376

0th50th100th

Percentile = (repositories below + half of 5 tied repositories) ÷ 376.

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code signatures →Cursor Agent commitsBrowse repositories with detected Cursor Agent signatures →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 plotly/plotly.js

Scan another repository

Try