The backend—i.e. core services, APIs, and REST endpoints—to Jupyter web applications.
C-Rank Grade: B (Solid) - 41/100
External PR Merge Rate: 19%
Response Time: 20h
First Timer Success: -
jupyter-server/jupyter_server has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jupyter-server/jupyter_server respond to incoming external pull requests in approximately 19.5 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 41.4 places jupyter-server/jupyter_server in the B tier.
The external contributor pull request merge rate for jupyter-server/jupyter_server is 18.8%, based on public PR activity from non-core contributors.
jupyter-server/jupyter_server does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
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/jupyter-server/jupyter_server?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (23% approval). Large PRs (>500 lines) take ~94 hours (15% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
No cached good first issues currently tracked for jupyter-server/jupyter_server.
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 jupyter-server/jupyter_server, 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 jupyter-server/jupyter_server acknowledge new external contributions in approximately 19 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 18.8% were successfully merged into the primary branch.
jupyter-server/jupyter_server has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~19 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 41.4 places jupyter-server/jupyter_server in the Solid tier.
The external pull request merge rate is 18.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
jupyter-server/jupyter_server does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for jupyter-server/jupyter_server 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.