Review economics
parse-community/parse-server
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.
≥1%
Attributed
a floor
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#10610 ci: Skip CI checks for draft pull requests
0 reviews · 0h to merge
#10536 fix: `Parse.Query.explain` runs afterFind trigger on query plan results
1 reviews · 21.4d to merge
#10540 fix: Server crash from unhandled promise rejection when multiple Cloud Code validator fields fail
8 reviews · 20.4d to merge
#10556 fix: Install the latest Parse Server version in bootstrap.sh
1 reviews · 19.1d to merge
#10587 refactor: Bump @semantic-release/release-notes-generator from 14.1.0 to 14.1.1
3 reviews · 1h 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; reads 100 of 4322 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 parse-community/parse-server 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 parse-community/parse-server — 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