Review economics
Wei-Shaw/sub2api
Read from the 100 most recently merged pull requests ·
Pull requests with attributed agent authorship took 3.1× the time to merge of the rest.
≥2%
Attributed
a floor
3
Attributed PRs
97
Other PRs
100
Read
Attributed — the latest 3
The rest — the latest 5
#5223 feat(aliyun-captcha): 人机验证增加阿里云验证码 2.0
0 reviews · 30h to merge
#5268 fix(auth-ui): 第三方 OAuth 建号提交前必须持有验证码票据
0 reviews · 0h to merge
#5261 新增腾讯天御验证码认证门禁
0 reviews · 1h to merge
#5224 fix(subscription): serialize concurrent renewals
0 reviews · 23h to merge
#5177 fix(openai-ws): preserve terminal event on lease loss
0 reviews · 2.2d to merge
How this was measured
2% 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; 11 PRs came off an agent branch with no commit attribution, so the real share runs higher; reads 100 of 1320 merged PRs — the rest have not been analyzed yet.
Detected: Claude Code, OpenAI Codex.
“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 Wei-Shaw/sub2api 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 Wei-Shaw/sub2api — 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