Review economics
tmate-io/tmate
Read from the 10 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥4%
Attributed
a floor
1
Attributed PRs
9
Other PRs
10
Read
Attributed — the latest 1
The rest — the latest 5
#328 Fix potential vulnerable cloned function
0 reviews · 0h to merge
#271 Add CI build checks
0 reviews · 18h to merge
#259 chore: add FUNDING.yml
0 reviews · 28h to merge
#228 Forwarding patches made to the debian package
0 reviews · 123.2d to merge
#236 add basic information for -a option in man page and help text
0 reviews · 53.2d to merge
How this was measured
4% of merged commits carry agent attribution — a floor, not the share; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work.
Detected: Claude Code.
“Attributed” means a commit carried an agent’s signature — a co-author trailer, an agent commit identity, or an agent bot account. Tools that only complete code inline leave no such mark, so the other column is “rest”, not “human-written”. Full method and its limits
The badge reads this repo’s current report, so it follows the number.
Tell me when this moves
We re-read tmate-io/tmate weekly and email only when the number changes materially.
Read your own repos
This one is public. For a private repo, run the same read locally through your own GitHub credentials — nothing is installed and nothing is sent to us.
npx @ambera/review-taxWant this continuously on tmate-io/tmate — each pull request paired to the task it came from, and the work graded from its review loop rather than its diff size? Claim this repo in Forge
Browse every repo people have read · Read a different repository