Review economics
junit-team/junit4
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.
—
Attributed
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#1790 Fix GitHub Actions build
0 reviews · 0h to merge
#1740 Fix compile error on JDK 18 and later
1 reviews · 186.4d to merge
#1786 Document that JUnit 4 is in maintenance mode
2 reviews · 3.1d to merge
#1785 Migrate to Maven Central Publisher Portal
1 reviews · 0h to merge
#1687 Mark ThreadGroups created by FailOnTimeout as daemon groups
1 round · 8 reviews · 25h 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; reads 100 of 473 merged PRs — the rest have not been analyzed yet.
“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 junit-team/junit4 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 junit-team/junit4 — 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