Review economics
vnotex/vnote
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
#2725 feat(macos): capture selected text as a note via a system Service
0 reviews · 5h to merge
#2724 Fix CI: avoid NSDMI-in-default-argument rejected by GCC/Clang
0 reviews · 6h to merge
#2714 ci(linux): make bundled libfontconfig removal robust to path/absence
0 reviews · 1h to merge
#2707 fix(export): scope MathJax PNG rasterization and harden PDF export
0 reviews · 0h to merge
#2701 fix: PDF export MathJax SVG-to-PNG conversion and render-ready signaling and use-after-free in exportdialog2
0 reviews · 8.9d 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 209 merged PRs — the rest have not been analyzed yet.
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 vnotex/vnote 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 vnotex/vnote — 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