Review economics
SonarSource/sonarqube
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
#3321 Copy of master
1 reviews · 22h to merge
#2555 SONAR-9875 Add branch= param to /api/navigation/component
8 reviews · 6.7d to merge
#2472 SONAR-9626 update log messages
2 reviews · 1h to merge
#2460 SONAR-9616 Do not include branch name in quality gate notifs when main
1 reviews · 1h to merge
#2450 SONAR-9616 Fix notifications on branches
3 reviews · 8h 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 2188 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 SonarSource/sonarqube 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 SonarSource/sonarqube — 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