A modern Jellyfin dashboard for live sessions, user stats, recently added media, libraries, downloads, calendars, webhooks, and backups.
C-Rank Grade: B (Solid) - 41/100
External PR Merge Rate: 14%
Response Time: 14d
First Timer Success: -
Nerdy-Technician/JellyGlance 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 Nerdy-Technician/JellyGlance respond to incoming external pull requests in approximately 340.8 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.0 places Nerdy-Technician/JellyGlance in the B tier.
The external contributor pull request merge rate for Nerdy-Technician/JellyGlance is 14.3%, based on public PR activity from non-core contributors.
Nerdy-Technician/JellyGlance currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A modern Jellyfin dashboard for live sessions, user stats, recently added media, libraries, downloads, calendars, webhooks, and backups.
Active maintainer team in Nerdy-Technician/JellyGlance welcoming community pull requests and bug fixes.
Discussions in Nerdy-Technician/JellyGlance focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/Nerdy-Technician/JellyGlance?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 09:00 UTC (09: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 ~222 hours (18% approval). Large PRs (>500 lines) take ~1636 hours (15% approval). Keep your diff compact for rapid review.
Problem JellyGlance has no Czech translation, so Czech-speaking users have to use the app in English. Also, npm run i18n:sync rebuilds every locale from the en-GB keys only. Languages that need more plural forms than English (Czech and Polish use _few / _many) lose those keys every time the sync runs. Proposed solution Add a full cs-CZ translation (apps/web/public/locales/cs-CZ/translation.json) and list "Čeština" in the language picker. Update scripts/i18n-sync.mjs so it keeps plural variants (_few, _many, …) when their base key exists in en-GB. Implemented in #203.
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 Nerdy-Technician/JellyGlance, 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 Nerdy-Technician/JellyGlance acknowledge new external contributions in approximately 14 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 14.3% were successfully merged into the primary branch.
Nerdy-Technician/JellyGlance 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 ~14 days+. 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.0 places Nerdy-Technician/JellyGlance in the Solid tier.
The external pull request merge rate is 14.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Nerdy-Technician/JellyGlance 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 Nerdy-Technician/JellyGlance 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.