Review economics
openjdk/jdk
Read from the 20 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
—
Attributed
0
Attributed PRs
20
Other PRs
20
Read
The rest — the latest 5
#31996 Merge ff8f6e1ef7eae930a2c55af2fd13674c7b2f0cbc
2 reviews · 0h to merge
#31995 Merge c6aaf91d2bd6f231466d19fdde8a61eb90aeb61c
2 reviews · 1h to merge
#30878 Merge 99c2cd01c3f82b37ef7faac38a1b92a083c1ab91
1 reviews · 0h to merge
#29331 Merge 07f981f6b0bb8a7e444fd744791f73853e9fa325
3 reviews · 5h to merge
#29332 Merge 4b0189c444a061f4e1e4dd27e7980ebb81252284
3 reviews · 5h to merge
How this was measured
No commit in this window carries agent attribution, so there is no AI-authored share to read here — which is not evidence there is none; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work.
“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 openjdk/jdk 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 openjdk/jdk — 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