Review economics
abel533/Mapper
Read from the 58 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
1
Attributed PRs
57
Other PRs
58
Read
Attributed — the latest 1
The rest — the latest 5
#798 新增渐进式处理ProgressiveMapper，支持渐进式全量删除和渐进式记录处理
0 reviews · 1920.6d to merge
#793 feat:新增根据实体中的属性进行查询指定属性
1 reviews · 1937.0d to merge
#936 fix: 限制流水线权限
1 reviews · 77.4d to merge
#940 Fixed the non-deterministic behavior of tests in TkMapperServiceTest
1 reviews · 32h to merge
#922 5.x - 基于jdk17和spring boot3
0 reviews · 0h 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.
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 abel533/Mapper 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 abel533/Mapper — 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