Review economics
Jannchie/Historical-ranking-data-visualization-based-on-d3.js
Read from the 19 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
19
Other PRs
19
Read
The rest — the latest 5
#77 Fix the max_number logic
0 reviews · 445.1d to merge
#119 Remove Jq
0 reviews · 123.7d to merge
#121 增强颜色相关功能：允许用户自定义配色方案，允许使用外部文件指定label 的color 值
0 reviews · 122.3d to merge
#69 添加了几个新功能 & 修复bug
0 reviews · 22.8d to merge
#72 Change color code to Hex, Update some English wording
0 reviews · 21h 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 Jannchie/Historical-ranking-data-visualization-based-on-d3.js 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 Jannchie/Historical-ranking-data-visualization-based-on-d3.js — 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