Review economics
99designs/aws-vault
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.
—
Attributed
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#1272 Update homebrew instructions
0 reviews · 106.0d to merge
#1256 Fix documentation about SDK's supporting AWS_CONTAINER_CREDENTIALS_FULL_URI
1 reviews · 411.1d to merge
#1270 chore: Update README with fork info
9 reviews · 203.9d to merge
#631 Handle OIDC caching for new keyring entries
0 reviews · 3h to merge
#1238 Update docs describing `sso_role_name` parameter
0 reviews · 68.2d to merge
How this was measured
No commit in this window carries agent attribution, so there is no AI-authored share to read here — which is not evidence there is none; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work; reads 100 of 341 merged PRs — the rest have not been analyzed yet.
“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 99designs/aws-vault 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 99designs/aws-vault — 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