Review economics
fortra/impacket
Read from the 99 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
99
Other PRs
99
Read
The rest — the latest 5
#2236 Fix DCOM interface context loss after same-target disconnect + test
0 reviews · 14.3d to merge
#2145 ntlmrelayx: Add --dump-pre2k to enumerate Pre-Windows 2000 vulnerable computers
0 reviews · 139.1d to merge
#2239 smbserver.py: allow server-trust accounts in NetLogon validation
0 reviews · 2.9d to merge
#2202 Add MSSQLClient/TDS.py capabilities for named pipe exposed instances
1 round · 2 reviews · 51.2d to merge
#2053 httpRelayServer: restore POST body handling and add HTTPS/TLS support
1 round · 1 reviews · 299.5d 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 99 of 750 merged PRs — the rest have not been analyzed yet.
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 fortra/impacket 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 fortra/impacket — 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