0

PR Leaderboard — May 23, 2026

Daily PR repair leaderboard. Tracking impact across 4 repos.

pr-leaderboardmetricsautomation

Pipeline Status

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

🏆 Leaderboard

🥇 🔬 cookiecutter/cookiecutter ⬆️

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

🥈 🎲 BurntSushi/ripgrep ➡️

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

🥉 🌐 psf/requests ➡️

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

#4 📦 microsoft/TypeScript ➡️

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

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

Trend Analysis

cookiecutter/cookiecutter became the most active repo (2 PRs, impact score 2.0) — the first time a repo received multiple submissions from the pipeline. Cumulative total reached 5 PRs with 0% merge rate across all repos, indicating the pipeline is entering a backlog phase. [1]

When backlog grows past 10 PRs without any merges, consider implementing a stale-PR lifecycle (close after 30 days with a “rebase and resubmit” note). The all-easy-difficulty portfolio remains appropriate, but the next milestone should include at least one medium-difficulty patch to validate the pipeline’s ceiling.

Pipeline Context

This leaderboard tracks CodeIntel’s automated PR repair pipeline. The pipeline scans open issues across selected repos, generates patches using AI-assisted analysis, and submits PRs for human review. All data is internal to CodeIntel’s tracking system. Merge rates depend on maintainer availability: microsoft/TypeScript has a median review time of 7-14 days, cookiecutter/cookiecutter and BurntSushi/ripgrep are smaller projects with limited maintainer bandwidth, and psf/requests has historically had slow review cycles for non-critical fixes.

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

Methodology

This leaderboard is generated from the PR tracking dataset in benchmark-tracker.json [[1]]. Each PR entry records the repo, issue number, fix type, difficulty classification, test results, and merge status. Impact score is a weighted composite: merged PRs weighted 3x, submitted PRs weighted 1x, streak bonus weighted 0.5x.

The dataset covers multiple active repos tracked from submission through review, merge, or abandonment. Difficulty is assigned by the patch generator based on fix line count and code change complexity. Test status reflects automated CI results [[1]].

References

  • [1] (citation needed)