Review economics
Masterminds/glide
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
#1060 Updating dependencies to pull in bug fixes
0 reviews · 0h to merge
#1033 Fix segfault with Glide 0.13.2 when stripping Godep workspace
2 reviews · 252.0d to merge
#1056 crypto ed25519 added to stdlib in go1.13
0 reviews · 21.0d to merge
#1023 Updating travis through 1.11
0 reviews · 0h to merge
#956 Issue 955
0 reviews · 5h 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 195 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 Masterminds/glide 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 Masterminds/glide — 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