Review economics
GrapesJS/grapesjs
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
1
Attributed PRs
99
Other PRs
100
Read
Attributed — the latest 1
The rest — the latest 5
#6803 Release GrapesJS core latest: v0.23.4
0 reviews · 0h to merge
#6799 Deselect components on removal
1 reviews · 6.3d to merge
#6801 build(deps-dev): bump postcss from 8.5.10 to 8.5.18
0 reviews · 46h to merge
#6798 Fix stale drop target on slow drags in sorter
1 reviews · 6.3d to merge
#6802 Improve data source binding performance for direct record-based resolvers
0 reviews · 0h 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 739 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 GrapesJS/grapesjs 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 GrapesJS/grapesjs — 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