Review economics
mem0ai/mem0
Read from the 100 most recently merged pull requests ·
Pull requests with attributed agent authorship took only 0.9× the reviews submitted of the rest.
≥2%
Attributed
a floor
3
Attributed PRs
97
Other PRs
100
Read
Attributed — the latest 3
The rest — the latest 5
#6793 SEO & metadata audit: trim Dream page description under 160 chars
1 reviews · 0h to merge
#6790 fix(zapier): require user_id on Add Memory
1 reviews · 4h to merge
#6791 chore(n8n): route package contact to integrations@mem0.ai
1 reviews · 0h to merge
#6377 fix(ts-oss): strip identity scope from add() metadata
6 reviews · 17.3d to merge
#6656 fix(memory): stop add() metadata from setting a memory's identity scope
2 reviews · 6.0d 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; 1 PR came off an agent branch with no commit attribution, so the real share runs higher; reads 100 of 2475 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 mem0ai/mem0 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 mem0ai/mem0 — 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