Review economics
v2fly/v2ray-core
Read from the 100 most recently merged pull requests ·
Pull requests with attributed agent authorship took 1.0× the time to merge of the rest.
≥4%
Attributed
a floor
3
Attributed PRs
97
Other PRs
100
Read
Attributed — the latest 3
The rest — the latest 5
#3739 Chore: bump github.com/go-playground/validator/v10 from 10.30.2 to 10.30.3
0 reviews · 64.9d to merge
#3772 Chore: bump github.com/pires/go-proxyproto from 0.12.0 to 0.15.0
0 reviews · 25.9d to merge
#3769 Chore: bump github.com/go-chi/chi/v5 from 5.3.0 to 5.3.1
0 reviews · 25.9d to merge
#3771 Chore: bump google.golang.org/grpc from 1.82.1 to 1.83.0
0 reviews · 25.9d to merge
#3770 Chore: bump github.com/quic-go/quic-go from 0.59.1 to 0.61.0
0 reviews · 25.9d to merge
How this was measured
4% 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 1037 merged PRs — the rest have not been analyzed yet.
Detected: 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 v2fly/v2ray-core 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 v2fly/v2ray-core — 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