Review economics
langchain-ai/local-deep-researcher
Read from the 40 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥3%
Attributed
a floor
2
Attributed PRs
38
Other PRs
40
Read
Attributed — the latest 2
The rest — the latest 5
#136 Bump aiohttp from 3.14.1 to 3.14.3 in the uv group across 1 directory
0 reviews · 10h to merge
#134 Bump the uv group across 1 directory with 2 updates
0 reviews · 16.1d to merge
#133 Bump aiohttp from 3.14.0 to 3.14.1 in the uv group across 1 directory
0 reviews · 8.8d to merge
#131 Bump the uv group across 1 directory with 4 updates
0 reviews · 10.2d to merge
#129 Bump lxml from 6.0.0 to 6.1.0 in the uv group across 1 directory
0 reviews · 48.3d to merge
How this was measured
3% 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.
Detected: Claude Code, GitHub Copilot coding agent.
“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 langchain-ai/local-deep-researcher 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 langchain-ai/local-deep-researcher — 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