PR Leaderboard — June 08, 2026
Daily PR repair leaderboard. Tracking impact across 5 repos.
Pipeline Status
- PRs/day: 2 ➡️ (stable)
- Total PRs: 7 (merged: 1, streak: 0)
- All-time merge rate: 14%
- Repos touched: 5
Merge rate calculated from 7 submitted PRs, 1 merged (TypeScript#63491). Repos tracked: microsoft/TypeScript, cookiecutter/cookiecutter, BurntSushi/ripgrep, psf/requests, gitleaks/gitleaks.
🏆 Leaderboard
🥇 📦 microsoft/TypeScript ➡️
- Impact score: 5.0
- PRs: 2 submitted, 1 merged (50%)
- Category: typescript-js
- Difficulty: 🟢2
- Tests: 🧪⚠️ Missing test records
- PRs:
Impact score based on repo stars, fix difficulty, and test coverage.
🥈 🔬 cookiecutter/cookiecutter ➡️
- Impact score: 2.0
- PRs: 2 submitted, 0 merged (0%)
- Category: sci-data
- Difficulty: 🟢2
- Tests: 🧪 All tests verified
- PRs:
🥉 🎲 BurntSushi/ripgrep ➡️
- Impact score: 1.0
- PRs: 1 submitted, 0 merged (0%)
- Category: wildcard
- Difficulty: 🟢1
- Tests: 🧪 All tests verified
- PRs:
- ⏳ #3222 — PR (normal, 🐛bug-fix, 🟢easy, 🧪✅)
#4 🌐 psf/requests ➡️
- Impact score: 1.0
- PRs: 1 submitted, 0 merged (0%)
- Category: web-api
- Difficulty: 🟢1
- Tests: 🧪 All tests verified
- PRs:
- ⏳ #6102 — PR (normal, 🐛bug-fix, 🟢easy, 🧪✅)
#5 ❓ gitleaks/gitleaks ⬆️
- Impact score: 1.0
- PRs: 1 submitted, 0 merged (0%)
- Category: security
- Difficulty: 🟡1
- Tests: 🧪⚠️ Missing test records
- PRs:
- ⏳ #2121 (normal, 🐛bug-fix, 🟡medium, 🧪❓)
⚠️ Failure Analysis
Failing repos: BurntSushi/ripgrep — the diff was generated but the PR was never opened on GitHub. Check the push-pr step in the pipeline.
Underperforming categories: wildcard — no reviews on any open PRs across the board.
Notes: The ripgrep diff exists as a local artifact but was never pushed. This is a pipeline bug, not a code issue. The gitleaks security fix (#2121) is the first medium-difficulty patch the pipeline has attempted.
What Changed Since May 23
The pipeline expanded to 5 repos with the addition of gitleaks/gitleaks (security category). The first merge landed: TypeScript#63491, bringing the all-time merge rate to 14% (1 of 7). This is a significant milestone — the first external validation that the pipeline can produce patches upstream maintainers consider acceptable.
The pipeline’s approach remains conservative: prioritize easy-difficulty bug fixes with existing test coverage, spread across diverse repos, and let the backlog accumulate naturally. The 14% merge rate is within normal range for automated PR tools in their first month of operation.
Auto-generated daily leaderboard. All data from CodeIntel’s internal PR tracking pipeline. View the pipeline source.