Review economics
SerenityOS/serenity
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
#26918 Kernel: Give all declarations hidden visibility (to avoid GOT loads)
1 reviews · 2.8d to merge
#26919 LibPDF+pdf: Add a --strict option
1 reviews · 6h to merge
#26840 Kernel/x86_64: Fix booting with time=legacy
2 reviews · 4.8d to merge
#26913 Kernel/Net: Avoid a bunch of MMIO accesses in the E1000 driver
9 reviews · 3.3d to merge
#26910 strace: A bunch of improvements
2 reviews · 24h 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 20124 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 SerenityOS/serenity 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 SerenityOS/serenity — 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