Review economics
didi/booster
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.
≥7%
Attributed
a floor
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#495 Remove agp 9.0 substitute module.
0 reviews · 2h to merge
#479 Fix TransformContext properties
0 reviews · 0h to merge
#478 升级javassist版本 ，否则宿主工程使用JavaVersion.VERSION_17 编译时，会出现字节码版本不同 导致javass…
1 reviews · 5.0d to merge
#467 Fix `Variant.localAndroidResources`
0 reviews · 0h to merge
#466 Fix `booster-task-graph`
0 reviews · 0h to merge
How this was measured
7% 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 165 merged PRs — the rest have not been analyzed yet.
Detected: 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 didi/booster 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 didi/booster — 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