Review economics
typeorm/typeorm
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.
≥2%
Attributed
a floor
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#12416 refactor!: extract legacy naming strategies
4 reviews · 8.4d to merge
#12711 fix(persistence): keep many-to-many junction rows when the relation is not loaded
2 reviews · 10.9d to merge
#12702 fix: guard metadata access in InsertQueryBuilder for raw-table upsert
3 reviews · 6.4d to merge
#12726 fix: resolve relation values for join columns inside embedded entities
2 reviews · 19h to merge
#12629 fix(query-builder): reject empty where criteria on update and delete operations
11 reviews · 11.8d 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; reads 100 of 2668 merged PRs — the rest have not been analyzed yet.
Detected: GitHub Copilot coding agent, Claude Code.
“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 typeorm/typeorm 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 typeorm/typeorm — 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