Review economics
yjs/yjs
Read from the 99 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥1%
Attributed
a floor
2
Attributed PRs
97
Other PRs
99
Read
Attributed — the latest 2
The rest — the latest 5
#789 docs(readme): add Deln0r/ygo to the Ports list
0 reviews · 0h to merge
#784 README: add mutative-yjs bindings
0 reviews · 1h to merge
#778 fix stale JSDoc examples after v14 API rename
0 reviews · 27.6d to merge
#775 Fix undo of attr-change + delete corrupting remote sync (#757)
2 reviews · 20.3d to merge
#773 write incident response plan
0 reviews · 0h to merge
How this was measured
1% 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 99 of 184 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 yjs/yjs 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 yjs/yjs — 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