Review economics
go-resty/resty
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
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#1188 fix: stop multipart producer after early response without race/hang
0 reviews · 4.2d to merge
#1187 feat: add support for the HTTP QUERY method (RFC 10008)
1 round · 3 reviews · 2.9d to merge
#1184 test: Fix environment-dependent flaky assertion in TestTraceInfoOnTimeoutWithSetTimeout
0 reviews · 3.3d to merge
#1183 chore: bump version to 3.0.0-rc.3+devrc4 for next dev iteration
0 reviews · 0h to merge
#1182 release: version bump to v3.0.0-rc.3
0 reviews · 0h 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 428 merged PRs — the rest have not been analyzed yet.
Detected: Cursor 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 go-resty/resty 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 go-resty/resty — 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