Open-source media request and discovery manager for Jellyfin, Plex, and Emby.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 41%
Response Time: 16h
First Timer Success: 13%
seerr-team/seerr has a recorded first-timer success rate of 12.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in seerr-team/seerr respond to incoming external pull requests in approximately 16.1 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 56.8 places seerr-team/seerr in the A tier.
The external contributor pull request merge rate for seerr-team/seerr is 41.3%, based on public PR activity from non-core contributors.
seerr-team/seerr currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source media request and discovery manager for Jellyfin, Plex, and Emby.
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in seerr-team/seerr.
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/seerr-team/seerr?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (52% approval). Large PRs (>500 lines) take ~115 hours (19% approval). Keep your diff compact for rapid review.
Description When a user hits their movie or TV quota, the request is rejected outright. MediaRequest.request() throws QuotaRestrictedError (server/entity/MediaRequest.ts, ~lines 150–166), which the route maps to a 403. Nothing is created, so an admin never sees it and the user has no way to ask for an exception. The only bypass is ignoreQuota, which requires MANAGE_REQUESTS and is an admin action. Users who are over quota but have a legitimate need can't ask for approval. Desired Behavior When a non-admin user exceeds their quota, instead of a 403, create the request in PENDING status with a flag (for example quotaExceeded: true) so it: shows in the pending queue with a visible "over quota" badge, is approved through the existing flow, which then bypasses the quota check for that request. The frontend would show "Over quota. Submit for approval?" in place of the error. Quotas are a reasonable default, but a hard stop with no path forward means users either ask an admin out of band
Description GET /avatarproxy/:jellyfinUserId never sends a response when the path parameter fails the 32-hex validation check. The request hangs until the client or an upstream proxy times out. In server/routes/avatarproxy.ts, the handler throws when the parameter does not match /^[a-f0-9]{32}$/, and the catch block logs the error but never calls res: } catch (e) { logger.error('Failed to proxy avatar image', { errorMessage: e.message, }); } Since nothing is sent and next(e) is not called, Express keeps the request open indefinitely. The route is mounted outside /api/v1 (server/index.ts), so it is not covered by the OpenAPI validator and requires no authentication — an unauthenticated request can hold a server connection open with no rate limit. Behind a reverse proxy this surfaces as a gateway timeout (Cloudflare returns 524 after 100s). Still present on develop as of this report. Suggested fix Send a response on the error path, e.g.: } catch (e) { logger.error('Failed to
Description Currently all calls to external services are made with the default 'axios' user agent. Good practice would be to use a Seerr specific user agent. Desired Behavior user-agent header added to all Axios.Create calls or via an interceptor Additional Context No response Search Existing Issues Yes, I have searched existing issues. Code of Conduct I agree to follow Seerr's Code of Conduct
Description The ability to choose a discussion thread for each type of notification. Desired Behavior Improve the Discord notification agent so that it can send messages in thread. Like Mee6 Bot. Additional Context No response Search Existing Issues Yes, I have searched existing issues. Code of Conduct I agree to follow Seerr's Code of Conduct
Description The current API key is tied to the first/root user account. This means any integration (bots, scripts, automation) that calls the API acts with admin-level identity, and there's no way to scope or audit API access per user. Rotating the key also affects all integrations at once. Desired Behavior Allow each user to generate their own personal API key from their profile settings. The key would act on behalf of that user — respecting their role and permissions — rather than always acting as admin. Admin users could optionally view/revoke all personal keys Additional Context No response Search Existing Issues Yes, I have searched existing issues. Code of Conduct I agree to follow Seerr's Code of Conduct
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 seerr-team/seerr, 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 seerr-team/seerr acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 41.3% were successfully merged into the primary branch.
seerr-team/seerr has a recorded first-timer success rate of 12.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 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 56.8 places seerr-team/seerr in the Welcoming tier.
The external pull request merge rate is 41.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, seerr-team/seerr 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 seerr-team/seerr 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.