Review economics
graphql/graphiql
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.
—
Attributed
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#4448 feat(graphiql-react): expose customScalarSchemas for the variable editor
2 reviews · 2.4d to merge
#4452 Bump body-parser from 1.20.4 to 1.20.6
0 reviews · 19h to merge
#4453 Bump joi from 17.4.0 to 17.13.4
0 reviews · 18h to merge
#4454 v6: Move the response sub-components into `response-editor` and out of the public barrel
0 reviews · 0h to merge
#4431 v6: lock down the `@graphiql/react` public surface before 6.0.0
0 reviews · 14.1d 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; reads 100 of 2369 merged PRs — the rest have not been analyzed yet.
“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 graphql/graphiql 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 graphql/graphiql — 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