0

PR Leaderboard — May 22, 2026

Daily PR repair leaderboard. Tracking impact across 4 repos.

pr-leaderboardmetricsautomation

Pipeline Status

  • PRs/day: 2 ➡️ (stable)
  • Total PRs: 4 (merged: 0, streak: 0)
  • All-time merge rate: 0%
  • Repos touched: 4

🏆 Leaderboard

🥇 🎲 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, 🧪✅)

🥈 🌐 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, 🧪✅)

🥉 📦 microsoft/TypeScript ➡️

  • Impact score: 1.0
  • PRs: 1 submitted, 0 merged (0%)
  • Category: typescript-js
  • Difficulty: 🟢1
  • Tests: 🧪 All tests verified
  • PRs:
    • ⏳ #63480 — PR (normal, 🐛bug-fix, 🟢easy, 🧪✅)

#4 🔬 cookiecutter/cookiecutter ⬆️

  • Impact score: 1.0
  • PRs: 1 submitted, 0 merged (0%)
  • Category: sci-data
  • Difficulty: 🟢1
  • Tests: 🧪 All tests verified
  • PRs:
    • ⏳ #2219 — PR (normal, 🐛bug-fix, 🟢easy, 🧪✅)

Auto-generated daily leaderboard. Next update: tomorrow 14:00 PST.

Trend Analysis

The pipeline expanded to 4 repos (new: cookiecutter/cookiecutter) while maintaining 2 PRs/day velocity from the May 19 baseline. Repo diversity increased from 3 to 4, reducing single-repo dependency risk.

All 4 PRs remain easy-difficulty bug fixes — the pipeline has not yet attempted medium or hard-difficulty patches, which is appropriate for the validation phase. The trend to watch: as total PRs grow, the backlog of unmerged PRs will accumulate, and stale-PR cleanup will become necessary.

A practical rule of thumb: when backlog exceeds 10 open PRs without any merges, implement a stale-PR lifecycle policy (close after 30 days with a “rebase and resubmit” note). This keeps the backlog healthy and signals to maintainers that the bot respects their time.

Pipeline Context

All data above comes from CodeIntel’s automated PR repair pipeline. The pipeline scans open issues, generates patches via AI-assisted analysis, and submits PRs for human review. Merge rates depend entirely on maintainer availability — microsoft/TypeScript has a median review time of 7-14 days, while smaller projects like cookiecutter/cookiecutter can take longer due to limited maintainer bandwidth.

Auto-generated daily leaderboard. All data from CodeIntel’s internal PR tracking pipeline. View the pipeline source.