Review economics
shiyu-coder/Kronos
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
#243 fix: preserve batch dimension in tokenizer and predictor training
0 reviews · 3h to merge
#234 Fix data leakage in normalization window (#227)
0 reviews · 2.2d to merge
#232 fix: use torch.topk instead of calling top_k int parameter as a function in sample_from_logits
0 reviews · 3.9d to merge
#224 Fixes #223 : remove incompatible numpy pin from webui requirements
2 reviews · 34.4d to merge
#139 修改内容
0 reviews · 185.2d 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.
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 shiyu-coder/Kronos 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 shiyu-coder/Kronos — 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