Review economics
benfred/py-spy
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
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#848 Gate CLI dependencies behind optional `cli` feature flag
1 reviews · 16h to merge
#849 fix: get_mach_cpu_type do not mutate imutable variable with raw pointers
0 reviews · 21h to merge
#825 feat: Format function names with qualname for Python 3.11+
1 reviews · 99.8d to merge
#844 Minor code cleanups
0 reviews · 0h to merge
#779 Add support for native extensions on linux aarch64
1 reviews · 282.2d 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 305 merged PRs — the rest have not been analyzed yet.
Detected: OpenHands, Claude Code, OpenAI Codex.
“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 benfred/py-spy 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 benfred/py-spy — 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