Review economics
google/filament
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
#10251 filamentapp: refactor samples to common init method
6 reviews · 7.9d to merge
#10262 build(deps): bump brace-expansion from 5.0.8 to 5.0.9 in /build/common/upload-release-assets in the npm_and_yarn group across 1 directory
1 reviews · 38h to merge
#10152 variant removal: avoid traversing invalid specKey
3 reviews · 39.8d to merge
#10264 Add AbslStringify function to CString and CallStack
2 reviews · 4h to merge
#10252 opengl: Support external textures with mipmaps
1 reviews · 6.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; reads 100 of 6177 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 google/filament 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/filament — 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