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

Local to this browser

01Result

so-fancy/diff-so-fancy ↗

so-fancy/diff-so-fancy AI coding statistics: 0%

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

No signed agent commits found

No agent signatures were found in the last 171 considered commits. That is a real result, not a failure to measure.

It does not mean no AI was used here. A developer can use an agent and commit by hand without leaving a detectable git signature.

agent commits

171

other considered commits

—

agent contributors

—

largest contributor

02Drivers

What shapes this result

Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.

No agent signatures were detected, so there are no agent, mode, or timing drivers to break down.

03Evidence

Inspect the matches

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

No matched commit samples are available for this observation.

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	183
Merge commits removed	−10
CI / dependency bots removed	−2
Considered	171

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: so-fancy/diff-so-fancy
Default branch: next
Resolved HEAD: 8c03d4a5023c47087a35a34f489c242098b0a65c ↗
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.

CohortPerl · 1 eligible repositories · at least 100 considered commits2026-09-18-v3.0 · February–September 15, 2026 · 1 of 2 ecosystem repositories excluded

Comparison withheld for a small cohort

Only 1 eligible repositories remain; qmmit requires at least 10 before showing a percentile. The cohort definition and sample size remain visible so the omission is auditable.

Continue exploring

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 so-fancy/diff-so-fancy

Scan another repository

Try