Review economics
valkey-io/valkey
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.
≥0%
Attributed
a floor
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#3465 fix: update maxmemory test to account for SDS pre-allocation memory
4 reviews · 118.9d to merge
#3611 Fix RDMA + IO threads re-entrancy and busy-loop via connection postpone masks
15 reviews · 92.2d to merge
#4331 Deflake HRANDFIELD CASE 4 test with expired hash fields
3 reviews · 21h to merge
#4320 Fix io-thread race in slot migration establish response handler
1 reviews · 37h to merge
#4322 reset scan cursor when table is deleted
3 reviews · 28h to merge
How this was measured
0% 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 2046 merged PRs — the rest have not been analyzed yet.
Detected: Claude Code, Google Jules.
“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 valkey-io/valkey 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 valkey-io/valkey — 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