Review economics
lostindark/DriverStoreExplorer
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
#443 de-DE - fix typo, grammar, shortcuts and add some dev words
0 reviews · 0h to merge
#441 Update Language.fr-FR.resx
0 reviews · 38h to merge
#438 update Microsoft.Dism to Version 6.0.0 and changed TargetFramework to net472
0 reviews · 15h to merge
#434 Update Language.tr-TR.resx
0 reviews · 0h to merge
#354 Update Language.tr-TR.resx
0 reviews · 46h 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 158 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 lostindark/DriverStoreExplorer 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 lostindark/DriverStoreExplorer — 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