Review economics
VirusTotal/yara
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.
—
Attributed
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#2235 reject unknown object type in yr_object_create
1 reviews · 12h to merge
#2234 check stored digest length before comparing authenticode digests
1 reviews · 3h to merge
#2233 fix: build issues with OpenSSL 4.0.
0 reviews · 2h to merge
#2230 bound rule table index in OP_PUSH_RULE and OP_INIT_RULE
1 reviews · 4.5d to merge
#2224 bound tilde stream row-count read in dotnet_parse_tilde_2
1 reviews · 11.2d 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; reads 100 of 859 merged PRs — the rest have not been analyzed yet.
“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 VirusTotal/yara 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 VirusTotal/yara — 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