Review economics
golang/groupcache
Read from the 34 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
34
Other PRs
34
Read
The rest — the latest 5
#175 groupcache: add go.mod, update for Go 1.24
2 reviews · 23h to merge
#148 add back Context type as alias to context.Context
2 reviews · 27h to merge
#132 http: make http client request with context
0 reviews · 19.0d to merge
#131 Use standard library's context.Context
1 reviews · 24h to merge
#127 Format error string as per go style
0 reviews · 34h 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 golang/groupcache 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 golang/groupcache — 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