Pulse
2026-09-18-v3.0
Dataset
2026-09-18-v3.0
Ruleset
b2e8889c66f7
Scanned
2026-09-16
Window
February–September 15, 2026
Local to this browser

01Result

nodejs/node ↗

nodejs/node AI coding statistics: 0.6%

of 2,418 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
0.6% agent · top contributor 33.3%11 contributors
org-wide

Adoption is broad. Many contributors are committing agent-authored work, which is what a real organisational rollout looks like.

15
agent commits
2,403
other considered commits
11
agent contributors
33.3%
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

15assisted
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

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-020%183
2026-031.9%207
2026-041.1%278
2026-050.3%319
2026-060%266
2026-070%313
2026-081.1%539
2026-090.3%313

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic120.5%
Cursor AgentAnysphere20.1%
OpenAI CodexOpenAI10%

03Evidence

Inspect the matches

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

Matched commit samples

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 window2,528
Merge commits removed−0
CI / dependency bots removed−110
Considered2,418

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
nodejs/node
Default branch
main
Resolved HEAD
67e66b8e054a842a68fa3d1ea71709953141172a ↗
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 position20th percentile

Midrank percentile; equal shares split the tied positions.

Repository
0.6%
Cohort median
5.4%
Share rank
300 / 376
0th50th100th

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

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code signatures →Cursor Agent commitsBrowse repositories with detected Cursor Agent signatures →OpenAI Codex commitsBrowse repositories with detected OpenAI Codex 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 nodejs/node

Scan another repository

Try