Every number on this page comes from public repositories that nobody here chose — the mirror takes them from the GitHub archive, an npm feed and a search for AI commit trailers, visits each one once, and replays its own recent history through the gate. So these are measurements of what the gate says about strangers' code. They are not a measure of those repositories' quality, not a judgement of the people who wrote them, and not a forecast of what the gate would say about a repository somebody is paid to maintain. No repository is named anywhere on this site.
What the headline leaves out
prereg_parser and no_stamps are excluded from the refusal rate and from every table below. Between them they refused 68,748 commits. Neither is about the change: one refuses a commit whose message carries no pre-registration block, the other refuses a vendor stamp. On somebody else's history both fire on nearly every commit, because what they measure is when the gate arrived, not what the commit did.
What the scanner hit, by class
| class | scanner hits | precision |
|---|---|---|
| silent-catch | 214,724 | UNMEASURED |
| fetch-no-timeout | 60,390 | UNMEASURED |
| secret-in-log | 600 | UNMEASURED |
| money-write-no-idempotency | 221 | UNMEASURED |
| unbounded-zod-input | 95 | UNMEASURED |
| pii-in-log | 23 | UNMEASURED |
A hit is a place a rule fired on somebody's staged bytes. Whether it was worth firing is the rule's precision, and measuring that means reading the hits by hand and counting how many were real. Until that is done and the number is on the record, this column says UNMEASURED — which is a different claim from a low number, and a very different one from a high one.
The desk
| probe | worked | share |
|---|---|---|
| git | 2,388/2,388 | 100.0% |
| home | 2,388/2,388 | 100.0% |
| hook_shell | 2,180/2,388 | 91.3% |
| key_dir | 2,388/2,388 | 100.0% |
| link | 2,388/2,388 | 100.0% |
| package_manager | 1,911/2,388 | 80.0% |
| spawn | 2,388/2,388 | 100.0% |
| mode | desks | share |
|---|---|---|
| full | 1,737 | 72.7% |
| partial | 617 | 25.8% |
| report-only | 34 | 1.4% |
By the model the commit says wrote it
| model — declared by trailer, not verified | commits | refused | rate |
|---|---|---|---|
| claude-trailer | 25,170 | 9,797 | 38.9% |
| cursor | 1,803 | 880 | 48.8% |
| copilot | 491 | 170 | 34.6% |
| claude-code | 433 | 215 | 49.7% |
| codex | 343 | 116 | 33.8% |
| devin | 256 | 122 | 47.7% |
| gemini | 89 | 38 | 42.7% |
| aider | 7 | 2 | 28.6% |
Nothing here checked that a model wrote anything. A commit trailer is a string the committing tool puts in the message, anybody can write one by hand, and a commit written by a model whose tool writes no trailer appears in none of these rows. 28,592 commits carry a trailer this table recognises, against 43,773 replayed in total.
- of
- 94 of 2,547 repositories; the rest came from the archive and the npm feed
- interval
- 95% CI 3.0–4.5%
- as of
- 2026-09-21 (EDT)
- query
- q-bench
That share is of repositories, not of commits: how a repository was reached has one value per row, while a commit can carry two trailers and be counted twice. The other two feeds — the archive and the npm feed — select on no AI signal at all, which is what keeps this bench from being a survey of repositories that advertise themselves.