Review economics
zephyrproject-rtos/zephyr
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.
≥0%
Attributed
a floor
1
Attributed PRs
99
Other PRs
100
Read
Attributed — the latest 1
The rest — the latest 5
#111649 wch: ch32v20x: Add DT control of internal clock divisor and clock config check
1 round · 6 reviews · 47.8d to merge
#115076 Add to scheduled scanners: gcc analyzer + lsan/asan/ubsan with twister
7 reviews · 5.5d to merge
#115209 drivers: sdhc: set SDHC_INIT_PRIORITY to KERNEL_INIT_PRIORITY_DEVICE
2 reviews · 2.5d to merge
#114466 Modify the overlay to support mcxn947 nighthawk bluetooth
3 reviews · 12.6d to merge
#113532 Fix shell msleep
3 reviews · 22.2d to merge
How this was measured
0% 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 68430 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 zephyrproject-rtos/zephyr 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 zephyrproject-rtos/zephyr — 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