Review economics
debezium/debezium
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
#7763 debezium/dbz#2357 Fall back to row-wise writes for UNNEST batches with binary fields
1 reviews · 21h to merge
#7706 debezium/dbz#2258 Add `capture.mode` to physical standby example
0 reviews · 14.8d to merge
#7756 debezium/dbz#2235 Align JDBC TINYINT expectations with INT8 mapping
2 reviews · 40h to merge
#7585 [ci] fix informix actions
3 reviews · 36.0d to merge
#7736 debezium/dbz#2275 Close connection on non-transient connection errors…
7 reviews · 6.5d 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; reads 100 of 6367 merged PRs — the rest have not been analyzed yet.
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 debezium/debezium 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 debezium/debezium — 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