The Lean Computer Science Library (CSLib)
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 36%
Response Time: 2h
First Timer Success: 33%
leanprover/cslib has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in leanprover/cslib respond to incoming external pull requests in approximately 2.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 61.5 places leanprover/cslib in the A tier.
The external contributor pull request merge rate for leanprover/cslib is 36.0%, based on public PR activity from non-core contributors.
leanprover/cslib currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in leanprover/cslib welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/leanprover/cslib?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (45% approval). Large PRs (>500 lines) take ~11 hours (16% approval). Keep your diff compact for rapid review.
Binding in lambda calculi is notoriously prone to error, and isn't a problem where formalization is an immediate defense because this is a question of correct definitions. Especially because we will have multiple implementations of binding, I'd like to have a set of tests that give us a bit more confidence that we've written the correct definitions. I'd like to start with the existing locally nameless STLC and port something like what exists at https://github.com/sweirich/lambda-n-ways into a suite of tests. Help is welcome with this issue since I have somewhat limited time at the moment.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to leanprover/cslib, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of leanprover/cslib acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 36.0% were successfully merged into the primary branch.
leanprover/cslib has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 61.5 places leanprover/cslib in the Welcoming tier.
The external pull request merge rate is 36.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, leanprover/cslib currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for leanprover/cslib are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.