Official Elixir Language Server Protocol implementation
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 86%
Response Time: -
First Timer Success: 88%
expert-lsp/expert has a recorded first-timer success rate of 87.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in expert-lsp/expert respond to incoming external pull requests in approximately 0.0 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 67.5 places expert-lsp/expert in the A tier.
The external contributor pull request merge rate for expert-lsp/expert is 85.6%, based on public PR activity from non-core contributors.
expert-lsp/expert currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in expert-lsp/expert. Prompt code reviews with positive guidance for new contributors.
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/expert-lsp/expert?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (39% approval). Keep your diff compact for rapid review.
This issue is to audit the Engine code, and remove any unnecessary code that increases its size. The Engine gets compiled for each toolchain combination the user needs, so the larger the engine the longer it takes to compile on the fly, and the more disk space it needs to cache those engine builds. Besides that, the Engine was always intended to be small. Things to check: Dead code Forge code that is only used by Expert and never by the Engine (that is, Forge should contain only the code shared by Expert and Engine, whenever possible) Functionality implemented in the Engine that could live in the Expert app instead
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 expert-lsp/expert, 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 expert-lsp/expert acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.6% were successfully merged into the primary branch.
expert-lsp/expert has a recorded first-timer success rate of 87.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 67.5 places expert-lsp/expert in the Welcoming tier.
The external pull request merge rate is 85.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, expert-lsp/expert 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 expert-lsp/expert 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.