Review economics
dotnet/MQTTnet
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.
≥0%
Attributed
a floor
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#2254 Fix default TLS certificate validation (BREAKING CHANGE)
0 reviews · 3.4d to merge
#2247 Client: Tolerate late acknowledgement packets (#2078, #2079)
1 reviews · 41.0d to merge
#2253 Fix keep alive ping send timeout disconnect handling
1 reviews · 22h to merge
#2252 Migrate to SLNX
0 reviews · 41h to merge
#2251 Add support for pluggable stream provider to enable SOCKS5 proxies
0 reviews · 28.8d to merge
How this was measured
0% 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; reads 100 of 383 merged PRs — the rest have not been analyzed yet.
Detected: GitHub Copilot coding agent.
“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 dotnet/MQTTnet 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 dotnet/MQTTnet — 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