Review economics
chenshuo/muduo
Read from the 89 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
89
Other PRs
89
Read
The rest — the latest 5
#673 修复cpp17分支编译错误，offsetof需要cstddef头文件
0 reviews · 980.1d to merge
#729 fix missing header of noncopyable.h and coredump issue
0 reviews · 53.4d to merge
#705 [FIX] compile: missing <time.h> cause compile failure
0 reviews · 20.3d to merge
#703 fix build branch cpp17 on Kunpeng-920 where std::numeric_limits<long double>::digits10 == 33, instead of 18 on aarch64.
0 reviews · 8.5d to merge
#649 compile fix
0 reviews · 6h 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.
“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 chenshuo/muduo 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 chenshuo/muduo — 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