Review economics
pdfcpu/pdfcpu
Read from the 89 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
2
Attributed PRs
87
Other PRs
89
Read
Attributed — the latest 2
The rest — the latest 5
#1427 add CJK auto-wrap support for text watermarks
0 reviews · 24.9d to merge
#1397 Fix decrypt command argument handling
0 reviews · 4h to merge
#1352 fix: replace os.Exit() with panic() to prevent abrupt process termination
0 reviews · 6.1d to merge
#1304 Bump golang.org/x/crypto from 0.45.0 to 0.46.0
0 reviews · 6.0d to merge
#1212 Add word wrapping to form text field rendering
0 reviews · 111.0d 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.
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 pdfcpu/pdfcpu 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 pdfcpu/pdfcpu — 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