Review economics
bvaughn/react-error-boundary
Read from the 82 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
82
Other PRs
82
Read
The rest — the latest 5
#244 Add test coverage for error re-catch after reset
1 reviews · 8h to merge
#243 Remove unused docs and integration helpers
1 reviews · 13h to merge
#242 Clarify event handler error docs
9 reviews · 5h to merge
#240 Refresh error boundary docs and examples
3 reviews · 5h to merge
#239 Fix JSX attribute in ErrorBoundary example
1 reviews · 27h 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 bvaughn/react-error-boundary 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 bvaughn/react-error-boundary — 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