A powerful MCP toolkit for coding, providing semantic retrieval and editing capabilities - the IDE for your agent
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 63%
Response Time: 18h
First Timer Success: 66%
oraios/serena has a recorded first-timer success rate of 65.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in oraios/serena respond to incoming external pull requests in approximately 17.7 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 65.6 places oraios/serena in the A tier.
The external contributor pull request merge rate for oraios/serena is 62.8%, based on public PR activity from non-core contributors.
oraios/serena currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in oraios/serena. Maintains strict focus on technical quality and test standards.
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/oraios/serena?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 Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (79% approval). Large PRs (>500 lines) take ~85 hours (28% approval). Keep your diff compact for rapid review.
F# went from working sort of reliably, to some tests failing, to now most tests failing without any obviously related changes on our side. We just get wrong/incomplete answers from the LS process. I devoted a bit of time to it but couldn't find the source of the problems. Neither could Claude. Since this is low priority for Serena's core team, the F# tests have been completely disabled. Someone from the F# community could help out here, if interested
Seems like I was a bit premature with the merge: _ TestAnsibleLanguageServerBasics.test_hover_on_module_contains_documentation[ansible] _ self = <ansible.test_ansible_basic.TestAnsibleLanguageServerBasics object at 0x0000014E502EB310> language_server = <solidlsp.language_servers.ansible_language_server.AnsibleLanguageServer object at 0x0000014E54C42990> @pytest.mark.parametrize("language_server", [Language.ANSIBLE], indirect=True) def test_hover_on_module_contains_documentation(self, language_server: SolidLanguageServer) -> None: """Hover on ansible.builtin.package returns module documentation.""" # playbook.yml line 10 (0-indexed): "ansible.builtin.package:" result = language_server.request_hover("playbook.yml", 10, 8) > assert result is not None, "Expected hover info for ansible.builtin.package" E AssertionError: Expected hover info for ansible.builtin.package E assert None is not None @arikon could you have a look pls?
I disabled the respective tests on Windows; see commit d65a990. Perhaps a newer version will fix this and we can revert the commit. @takeokunn fyi
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 oraios/serena, 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 oraios/serena acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.8% were successfully merged into the primary branch.
oraios/serena has a recorded first-timer success rate of 65.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 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 65.6 places oraios/serena in the Welcoming tier.
The external pull request merge rate is 62.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, oraios/serena currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for oraios/serena 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.