Review economics
alibaba/page-agent
Read from the 100 most recently merged pull requests ·
Pull requests with attributed agent authorship took only 0.3× the time to merge of the rest.
≥3%
Attributed
a floor
3
Attributed PRs
97
Other PRs
100
Read
Attributed — the latest 3
The rest — the latest 5
#637 chore(deps): bump chalk from 5.6.2 to 6.0.0
1 reviews · 6.8d to merge
#635 chore(deps): bump @modelcontextprotocol/sdk from 1.29.0 to 1.30.0 in the production-dependencies group
0 reviews · 6.8d to merge
#632 chore(deps): bump fast-uri from 3.1.2 to 3.1.4
0 reviews · 30h to merge
#630 chore(deps): bump body-parser from 2.2.2 to 2.3.0
0 reviews · 44h to merge
#629 chore(deps-dev): bump the development-dependencies group with 16 updates
0 reviews · 3.0d to merge
How this was measured
3% 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 220 merged PRs — the rest have not been analyzed yet.
Detected: GitHub Copilot coding agent, Claude Code, 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 alibaba/page-agent 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 alibaba/page-agent — 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