Review economics
google/tsunami-security-scanner
Read from the 23 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
23
Other PRs
23
Read
The rest — the latest 5
#156 New templated variables
5 reviews · 81.1d to merge
#158 Fix typo in Tsunami documentation link
1 reviews · 31h to merge
#155 Bump requests from 2.32.4 to 2.33.0 in /plugin_server/py in the pip group across 1 directory
1 reviews · 13.9d to merge
#154 Security Fix: Prevent SSRF in core engine by blocking internal IPs
3 reviews · 18.4d to merge
#149 Add TsunamiSocketFactory with configurable timeout enforcement
1 reviews · 11.7d 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.
“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 google/tsunami-security-scanner 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 google/tsunami-security-scanner — 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