Subsonic music streaming app for Android
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 75%
Response Time: -
First Timer Success: 75%
ssalggnikool/Navic has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ssalggnikool/Navic respond to incoming external pull requests in approximately 0.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 63.5 places ssalggnikool/Navic in the A tier.
The external contributor pull request merge rate for ssalggnikool/Navic is 75.0%, based on public PR activity from non-core contributors.
ssalggnikool/Navic currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in ssalggnikool/Navic. Prompt code reviews with positive guidance for new contributors.
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/ssalggnikool/Navic?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (94% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
Feature explanation When listening to music where the lyrics are in a non-Latin writing system, add support for romanizing said lyrics either through a lyric provider (youly+ supports it, dont know about the other providers) or through a external/in device romanization api. Additional context No response Prerequisites I've checked existing issues to see if this already was requested I've ensured I am on the LATEST app version in case this was already added recently
Feature explanation I think that this currently look ugly, but it is only visual so not top priority Here is what I am talking about https://github.com/user-attachments/assets/5dc45b5c-7253-4d71-9c9b-f22ce9c72910 It would look much better if the navbar and the mini player would simply be fixed and not moving with the views Prerequisites I've checked existing issues to see if this already was requested I've ensured I am on the LATEST app version in case this was already added recently
This would allow features like a "shuffle all" button or play all songs from the songs tab to become feasible. Currently, just adding around 300 songs to the queue makes the app freeze for a solid 10 seconds. I tried this a while ago but I don't imagine it has changed. I have no idea what to do about this.
Feature explanation UI to view listening statistics for artists/songs/albums etc, this could be in many places: Play count labels throughout the app Detailed statistics screen opened via a button in SongSheet.kt or other sheets Dedicated statistic sections in artist screens or the library tab There could be graphs comparing artist play counts, showing top songs or more. I'm not entirely sure what an intuitive way to go about all of this would be, so as a last resort, we could just copy Last.FM's UI Additional context Implementation could be approached in many ways: Stick to what navidrome gives us Pros: simple Cons: only provides primitive statistics Integrate Last.FM/ListenBrainz API directly in-app Pros: powerful and detailed Cons: somewhat annoying to implement, and another thing for the user to setup Prerequisites I've checked existing issues to see if this already was requested I've ensured I am on the LATEST app version in case this was already added recently
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 ssalggnikool/Navic, 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 ssalggnikool/Navic acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.
ssalggnikool/Navic has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 63.5 places ssalggnikool/Navic in the Welcoming tier.
The external pull request merge rate is 75.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ssalggnikool/Navic 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 ssalggnikool/Navic 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.