The Free Software Media System - Server Backend & API
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 51%
Response Time: 7h
First Timer Success: 55%
jellyfin/jellyfin has a recorded first-timer success rate of 55.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jellyfin/jellyfin respond to incoming external pull requests in approximately 7.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 62.8 places jellyfin/jellyfin in the A tier.
The external contributor pull request merge rate for jellyfin/jellyfin is 51.2%, based on public PR activity from non-core contributors.
jellyfin/jellyfin currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in jellyfin/jellyfin.
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/jellyfin/jellyfin?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (64% approval). Large PRs (>500 lines) take ~115 hours (23% approval). Keep your diff compact for rapid review.
Description of the bug Upload a new Splashscreen in unsupported format and save other changes. Should not touch the image, but something happens (405 server code and jf-web can't access property "_sdk", r is undefined) Opened another web instance in different browser, but I can't reach the form. Reproduction steps Upload a JXL or so Upload fails (good), because it needs to be SkiaSharp readable/supported Save the form (save other changes) It changed something for image. What is the current bug behavior? 405 error from the server and SDK error in js-web What is the expected correct behavior? Only save supported formats (readable by SkiaSharp or mime-type), additionally would be best to be able to reach branding page for an update (never send 405 or make web more robust on failed response) Jellyfin Server version Master Specify commit id No response Specify unstable release number No response Specify version number No response Specify the build version Release Environment - OS: linux -
Description of the bug Hi, I'm unsure if this is a bug or intended behavior, but the POST /Auth/Keys api endpoint doesn't return the created API key. This means we need to GET /Auth/Keys and filter by app name which is not necessarily unique. Is there a reason not to return the API key on creation? If this is intended behavior feel free to close the issue. Thanks. Reproduction steps Obtain auth token POST /Auth/Keys Nothing gets returned by the API What is the current bug behavior? Nothing get returned. What is the expected correct behavior? The created API key gets returned in the response. Jellyfin Server version 10.11.6 Specify commit id No response Specify unstable release number No response Specify version number No response Specify the build version 10.11.6 Environment - OS: Debian 13 - Linux Kernel: 6.12.57+deb13-amd64 - Virtualization: No - Clients: N/A - Browser: N/A - FFmpeg Version: N/A - Playback Method: N/A - Hardware Acceleration: N/A - CPU Model: Intel(R) Xeon(R) CPU E
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 jellyfin/jellyfin, 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 jellyfin/jellyfin acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 51.2% were successfully merged into the primary branch.
jellyfin/jellyfin has a recorded first-timer success rate of 55.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 62.8 places jellyfin/jellyfin in the Welcoming tier.
The external pull request merge rate is 51.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jellyfin/jellyfin 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 jellyfin/jellyfin 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.