Review economics
grpc/grpc-java
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
#12971 xds: Add Http11ProxyUpstreamTransport to MessagePrinter
2 reviews · 2h to merge
#12948 xds: fix race condition in ext_proc client interceptor halfClose
1 reviews · 6.9d to merge
#12921 Fix: Append child channel configurators instead of overwriting
1 reviews · 14.0d to merge
#12782 xds: skip DiscoveryRequest for unsubscribed types on stream ready
2 reviews · 6.6d to merge
#12734 binder: Remove redundant ServerInbound.serverTransport field
1 reviews · 38.0d 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 7717 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 grpc/grpc-java 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-java — 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