Review economics
lionsoul2014/ip2region
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
#507 IPSub to IPAdd (clearer semantics)
0 reviews · 0h to merge
#503 fix: 修复`LoadHeaderFromBuff` 无长度检查，可能 panic的问题
0 reviews · 12h to merge
#502 fix: `SearcherPool` 关闭后 `BorrowSearcher()` 永久阻塞（死锁）
0 reviews · 11h to merge
#501 fix: `IPv4.IPCompare` 会修改输入切片（就地反转字节序）
0 reviews · 11h to merge
#500 fix：避免在 32 位平台上出现 maxFilePtr 溢出
0 reviews · 11h 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; 1 PR came off an agent branch with no commit attribution, so the real share runs higher; reads 100 of 161 merged PRs — the rest have not been analyzed yet.
Detected: OpenAI Codex.
“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 lionsoul2014/ip2region 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 lionsoul2014/ip2region — 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