Review economics
google/cadvisor
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
#3917 storage/stdout: nil-check Cpu, Network, and Memory stats
0 reviews · 3h to merge
#3918 fs/zfs: fall back to VFS when zfs stats are unavailable
0 reviews · 3h to merge
#3914 workflows: mirror release tags to lib/ module tags
0 reviews · 0h to merge
#3912 lib/manager: allow disabling container discovery
0 reviews · 8h to merge
#3913 build: discover bootstrap image tag instead of pinning it
0 reviews · 0h 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 1722 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 google/cadvisor 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 google/cadvisor — 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