Review economics
teamhanko/hanko
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
#2803 chore(deps-dev): bump sass from 1.100.0 to 1.102.0 in /frontend
1 reviews · 2h to merge
#2795 chore(deps): bump github.com/aws/aws-sdk-go-v2/config from 1.32.32 to 1.32.33 in /backend
1 reviews · 1h to merge
#2794 chore(deps): bump github.com/aws/aws-sdk-go-v2/service/kms from 1.55.1 to 1.55.2 in /backend
1 reviews · 1h to merge
#2739 fix: rate limit bypass
2 reviews · 16.1d to merge
#2734 fix: thirdparty allowed redirect bypass
1 reviews · 19.9d 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 1502 merged PRs — the rest have not been analyzed yet.
Detected: GitHub Copilot coding 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 teamhanko/hanko 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 teamhanko/hanko — 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