Review economics
apostrophecms/apostrophe
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.
≥2%
Attributed
a floor
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#5543 CON-47: field ids should not depend on md5, makes deployments too sensitive
1 reviews · 24h to merge
#5544 Fix styles wtih BOM ignored by browsers, leading to UI behavior change
1 reviews · 2h to merge
#5541 Regenerate session when invalid
1 round · 4 reviews · 2.0d to merge
#5542 efficient deep patches for widgets, allows effective in-context editing of complex pages
1 reviews · 1h to merge
#5540 Add document extraction system
1 reviews · 1h to merge
How this was measured
2% 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; reads 100 of 3440 merged PRs — the rest have not been analyzed yet.
Detected: Claude Code, GitHub Copilot coding agent.
“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 apostrophecms/apostrophe 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 apostrophecms/apostrophe — 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