Review economics
YaoApp/yao
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.
≥15%
Attributed
a floor
4
Attributed PRs
96
Other PRs
100
Read
Attributed — the latest 4
#1539 fix(sandbox): register container runners for local node with Docker
0 reviews · 0h to merge
#1538 feat: add Windows support
0 reviews · 0h to merge
#1536 fix(test): resolve PG test data isolation between parallel packages
0 reviews · 0h to merge
#1535 Add Windows test workflow (x64 + ARM64, SQLite + PG)
0 reviews · 0h to merge
The rest — the latest 5
#1571 Refactor API and enhance Git operations with new features
0 reviews · 0h to merge
#1570 feat(api): add new endpoints for file retrieval and service management
0 reviews · 0h to merge
#1569 Refactor inbox for task-based notifications and add skills discovery
0 reviews · 0h to merge
#1568 Disable tracing by default and update related tests
0 reviews · 0h to merge
#1567 Enhance security, GRPC resolution, and chat context management
0 reviews · 0h to merge
How this was measured
15% 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 1316 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 YaoApp/yao 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 YaoApp/yao — 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