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

cure53/DOMPurify ↗

cure53/DOMPurify AI coding statistics: 1.1%

of 184 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
1.1% 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.

2
agent commits
182
other considered commits
2
agent contributors
50%
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

2assisted
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%4
2026-030%16
2026-041.5%67
2026-050%41
2026-060%29
2026-0712.5%8
2026-080%13
2026-090%6

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

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic21.1%

03Evidence

Inspect the matches

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

Matched commit samples

  • 54cb7091 on GitHubAllow SVG dominant-baseline and text-orientation presentation attributes (Claude Code
  • d291155e on GitHubfix: apply SAFE_FOR_TEMPLATES scrub in RETURN_DOM path (#1241)Claude Code

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 window295
Merge commits removed−21
CI / dependency bots removed−90
Considered184

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
cure53/DOMPurify
Default branch
main
Resolved HEAD
38c4c37f084d1abea1e049128546ce567de5fbe4 ↗
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 position25th percentile

Midrank percentile; equal shares split the tied positions.

Repository
1.1%
Cohort median
5.4%
Share rank
283 / 376
0th50th100th

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

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code 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 cure53/DOMPurify

Scan another repository

Try