Review economics
jqlang/jq
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.
≥2%
Attributed
a floor
1
Attributed PRs
99
Other PRs
100
Read
Attributed — the latest 1
The rest — the latest 5
#3595 build(deps): bump actions/setup-python from 6 to 7 in the official-actions group
1 reviews · 19h to merge
#3586 Advance past the whole codepoint after a zero-width regex match
1 reviews · 32h to merge
#3555 docs: clarify join behavior on objects
1 reviews · 47.4d to merge
#3583 shtest: skip locale test if date lacks locale support
3 reviews · 2.9d to merge
#3574 Cast char to unsigned char before passing to isspace
1 reviews · 41h to merge
How this was measured
2% 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 708 merged PRs — the rest have not been analyzed yet.
Detected: OpenAI Codex, 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 jqlang/jq 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 jqlang/jq — 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