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

Local to this browser

01Result

codex-team/editor.js ↗

codex-team/editor.js AI coding statistics: 12.5%

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

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

12.5% 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.

1

agent commits

7

other considered commits

1

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

Agent share by month

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

Which agents

Agent	Vendor	Commits	Share
Cursor Agent	Anysphere	1	12.5%

03Evidence

Inspect the matches

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

Matched commit samples

5f45dabb on GitHubfix(ci): align workflow Node.js version with package engines (#3013)Cursor 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	8
Merge commits removed	−0
CI / dependency bots removed	−0
Considered	8

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: codex-team/editor.js
Default branch: next
Resolved HEAD: 30e1f792abac9a29b7d614273ff0f3b36ade2b64 ↗
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

Comparison withheld for low activity

This observation does not meet the 100-commit publication threshold. The cohort definition and sample size remain visible so the omission is auditable.

Continue exploring

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 codex-team/editor.js

Scan another repository

Try