Review economics
grpc/grpc-go
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.
≥1%
Attributed
a floor
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#9294 extproc: fix usages of testgrpc in test
1 reviews · 0h to merge
#9203 internal/transport: validate balancer and address metadata
6 reviews · 38.3d to merge
#9267 extproc: Implement client-side normal mode metrics
7 reviews · 10.6d to merge
#9268 credentials/alts: support max frame size negotiation via env var
12 reviews · 10.4d to merge
#9221 extauthz: parse base and override config for A92.
18 reviews · 28.6d to merge
How this was measured
1% 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; 1 PR came off an agent branch with no commit attribution, so the real share runs higher; reads 100 of 5079 merged PRs — the rest have not been analyzed yet.
Detected: OpenAI Codex, Claude Code, Gemini CLI, GitHub Copilot coding agent.
“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 grpc/grpc-go 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 grpc/grpc-go — 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