Pulse
2026-09-18-v3.0
Dataset
2026-10-27-catalog-ai-v2
Ruleset
b2e8889c66f7
Scanned
2026-10-27
Window
February–September 15, 2026
Catalog tracking observation. This repository is measured with the same fixed window and ruleset, but it is not part of the published benchmark or its aggregate claims.

Read-only mirror of https://gitlab.gnome.org/GNOME/gimp

GNOME/gimp ↗

GNOME/gimp AI coding statistics: 0%

of 2,411 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 2,411 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.

1
agent commits
2,410
other considered commits
1
agent contributors
100%
largest contributor

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.

Which agents

AgentVendorCommitsShare
GitHub CopilotGitHub10%

Inspect the matches

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

Matched commit samples

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,411
Merge commits removed−0
CI / dependency bots removed−0
Considered2,411

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

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 GNOME/gimp

Scan another repository