Review economics
PointCloudLibrary/pcl
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.
≥0%
Attributed
a floor
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#6406 Use same QT version as VTK.
2 reviews · 31h to merge
#6450 Disable tutorials since they are build by readthedocs.
1 reviews · 45.4d to merge
#6452 [FIX] gpu approx nearest unit test
2 reviews · 3.0d to merge
#6441 Add a toggle in getFitnessScore to respect user-provided indices in Registration
2 reviews · 22.6d to merge
#6445 CMake: Add 'USES_TERMINAL' to custom target for Ninja
1 reviews · 44h to merge
How this was measured
0% 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 100 of 3010 merged PRs — the rest have not been analyzed yet.
Detected: 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 PointCloudLibrary/pcl 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 PointCloudLibrary/pcl — 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