◆ 1.4/10

PR Leaderboard — June 14, 2026

Daily PR repair leaderboard. Tracking impact across 6 repos.

pr-leaderboardmetricsautomation

Pipeline Status

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

All metrics computed from the patch tracking dataset. Impact score = merged × 3 + submitted × 1 + streak × 0.5. [[1]]

🏆 Leaderboard

🥇 📦 microsoft/TypeScript ➡️

  • Impact score: 5.0 [[1]]
  • PRs: 2 submitted, 1 merged (50%) [[1]]
  • Category: typescript-js
  • Difficulty: 🟢2
  • Tests: 🧪⚠️ Missing test records
  • PRs:
    • ✅ #63480 — PR (normal, 🐛bug-fix, 🟢easy, 🧪✅)
    • ⏳ #25083 — PR (normal, 🐛bug-fix, 🟢easy, 🧪❓)

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

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

#5 ❓ gitleaks/gitleaks ➡️

  • Impact score: 1.0 [[1]]
  • PRs: 1 submitted, 0 merged (0%) [[1]]
  • Category: security
  • Difficulty: 🟡1
  • Tests: 🧪⚠️ Missing test records
  • PRs:
    • ⏳ #2121 (normal, 🐛bug-fix, 🟡medium, 🧪❓)

#6 🔬 sympy/sympy ➡️

  • Impact score: 1.0 [[1]]
  • PRs: 1 submitted, 0 merged (0%) [[1]]
  • Category: sci-data
  • Difficulty: 🟢1
  • Tests: 🧪⚠️ Missing test records
  • PRs:
    • ⏳ #24026 — PR (normal, 🐛bug-fix, 🟢easy, 🧪❓)

⚠️ Failure Analysis

Failing repos: microsoft/TypeScript Underperforming categories: wildcard Notes: ripgrep diff was generated but PR was never opened on GitHub. Check push-pr step. No reviews on any open PRs.

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

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. Trend direction compares today’s score against yesterday’s snapshot from leaderboard-archive.json [[1]].

The dataset covers multiple active repos. PRs are 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 from the runner environment [[1]]. Together these metrics provide a quantitative view of daily open-source maintenance activity across the tracked repo pool.

References

[1] PR tracking dataset — benchmark-tracker.json. https://github.com/techgeek/code-intel-blog/blob/main/production-patches/benchmark-tracker.json

📖 Related Reads

  • NoCode Insider — AI workflow automation with no-code tools, agents, and APIs

Cross-links automatically generated from CodeIntel Log.