Review economics
mobile-dev-inc/Maestro
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.
≥4%
Attributed
a floor
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#1292 Custom labels for readability and CLI output
2 reviews · 46.3d to merge
#2507 feat: add ability to switch and assert themes on iOS and Android: setDarkMode, toggleDarkMode, assertDarkMode & assertLightMode
19 reviews · 432.1d to merge
#3419 fix(android): bound adb-backed devtools sockets so webview tapOn can't hang or silently abort (MA-4111, MA-4090)
16 reviews · 26.0d to merge
#3470 feat: support element-relative point on swipe.from
1 reviews · 23h to merge
#3476 Prepare for release v2.8.0
1 reviews · 20h to merge
How this was measured
4% 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 1495 merged PRs — the rest have not been analyzed yet.
Detected: Claude Code, Cursor 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 mobile-dev-inc/Maestro 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 mobile-dev-inc/Maestro — 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