Review economics
alibaba/atlas
Read from the 32 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
—
Attributed
0
Attributed PRs
32
Other PRs
32
Read
The rest — the latest 5
#384 solve 'Caused by: com.google.protobuf.InvalidProtocolBufferException:…
0 reviews · 107.0d to merge
#383 指定资源重复打包失败
0 reviews · 19.1d to merge
#356 修复'java.lang.IllegalArgumentException: outDexFolder must be a folder'
1 reviews · 43h to merge
#362 3.0.1 rc88 fix sign npe
0 reviews · 5h to merge
#299 [atlas-gradle-plugin] fix #291 宿主修改layout资源后，动态部署没生效
0 reviews · 4.2d to merge
How this was measured
No commit in this window carries agent attribution, so there is no AI-authored share to read here — which is not evidence there is none; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work.
“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 alibaba/atlas 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 alibaba/atlas — 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