Review economics
microsoft/BitNet
Read from the 34 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥1%
Attributed
a floor
1
Attributed PRs
33
Other PRs
34
Read
Attributed — the latest 1
The rest — the latest 5
#596 Add VibeASR.cpp release to News
0 reviews · 16h to merge
#590 Revamp README with structured layout, News section, and Model Releases
0 reviews · 12h to merge
#589 Update README for BitNet Embedding 0.6B/270M release
0 reviews · 2h to merge
#587 Add BitNet Embeddings 0.6B/270M I2_S conversion guide and update README
1 reviews · 12h to merge
#584 Add F16 and I2_S GGUF conversion for bitnet-embeddings 0.6B and 270M models
1 reviews · 24h to merge
How this was measured
1% of merged commits carry agent attribution — a floor, not the share; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work.
Detected: Claude Code.
“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 microsoft/BitNet 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 microsoft/BitNet — 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