Review economics
leptos-rs/leptos
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.
≥1%
Attributed
a floor
1
Attributed PRs
99
Other PRs
100
Read
Attributed — the latest 1
The rest — the latest 5
#4832 Fix/islands router branch marker off by one
0 reviews · 22.9d to merge
#4836 fix: include submit input value in FormData when submitting Form
0 reviews · 11.9d to merge
#4842 test(integrations): gate static route tests on the `default` feature
0 reviews · 8h to merge
#4839 fix(router): keep `""` and `"/"` static segments as pass-through parents
0 reviews · 5h to merge
#4840 chore: make sure failing tests in CI actually cause failures
0 reviews · 20h to merge
How this was measured
1% 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 2261 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 leptos-rs/leptos 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 leptos-rs/leptos — 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