Review economics
miniflux/v2
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
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#4487 refactor: change existence-check helpers to return (bool, error)
0 reviews · 3.0d to merge
#4489 fix(ui): guard against nil session in CSRF middleware
0 reviews · 34h to merge
#4427 perf(internal): reorder some struct members
1 round · 1 reviews · 35.8d to merge
#4483 fix: enforce domain boundary in YouTube URL hostname check
0 reviews · 31h to merge
#4484 fix: log swallowed DB errors in existence-check helpers
0 reviews · 31h 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 2335 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 miniflux/v2 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 miniflux/v2 — 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