Review economics
Billionmail/BillionMail
Read from the 14 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥68%
Attributed
a floor
2
Attributed PRs
12
Other PRs
14
Read
Attributed — the latest 2
The rest — the latest 5
#256 feat: allow modifying the redis db from env vars
0 reviews · 4.2d to merge
#257 Update .gitattributes
0 reviews · 4.1d to merge
#203 ✨ (index.vue): add german language support to bt-config-provider
0 reviews · 9.8d to merge
#189 Added Turkish Language.
0 reviews · 8.7d to merge
#192 Create SECURITY.md
0 reviews · 0h to merge
How this was measured
68% 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 Billionmail/BillionMail 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 Billionmail/BillionMail — 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