Review economics
tmc/langchaingo
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
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#1403 vectorstores/milvus: complete migration to new SDK v2 client
0 reviews · 30.1d to merge
#1454 feat: Add Web search tool for OpenAI Client
0 reviews · 10.0d to merge
#1238 llms/openai: replace deprecated gpt-4-vision-preview with gpt-4o in TestMultiContentImage
3 reviews · 10.6d to merge
#1326 fix: ensure googleai schema conversion works with nested objects and arrays
0 reviews · 41.6d to merge
#1415 agents: allow match from multiple lines for parseOutput function
0 reviews · 10.3d 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 653 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 tmc/langchaingo 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 tmc/langchaingo — 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