Review economics
fabricjs/fabric.js
Read from the 100 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥1%
Attributed
a floor
1
Attributed PRs
99
Other PRs
100
Read
Attributed — the latest 1
The rest — the latest 5
#11063 chore(deps-dev): bump @playwright/test from 1.60.0 to 1.62.0
3 reviews · 36h to merge
#11065 test(), chore(): Various things i forgot
1 reviews · 10h to merge
#11064 feat(): Add backend network request callback
1 reviews · 23h to merge
#11062 chore(deps-dev): bump es-toolkit from 1.47.0 to 1.50.0
1 reviews · 1h to merge
#11059 chore(deps-dev): bump the vitest group with 4 updates
1 reviews · 0h to merge
How this was measured
1% 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; 9 PRs came off an agent branch with no commit attribution, so the real share runs higher; reads 100 of 2514 merged PRs — the rest have not been analyzed yet.
Detected: OpenAI Codex, 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 fabricjs/fabric.js 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 fabricjs/fabric.js — 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