A modern desktop client for Navidrome/Subsonic servers built with React and Electron.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 25%
Response Time: 3d
First Timer Success: 100%
victoralvesf/aonsoku has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in victoralvesf/aonsoku respond to incoming external pull requests in approximately 71.9 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 51.1 places victoralvesf/aonsoku in the B tier.
The external contributor pull request merge rate for victoralvesf/aonsoku is 25.0%, based on public PR activity from non-core contributors.
victoralvesf/aonsoku currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A modern desktop client for Navidrome/Subsonic servers built with React and Electron.
Active maintainer team in victoralvesf/aonsoku welcoming community pull requests and bug fixes.
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/victoralvesf/aonsoku?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 00:00 UTC (00: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 ~47 hours (31% approval). Large PRs (>500 lines) take ~345 hours (15% approval). Keep your diff compact for rapid review.
It would be great if we can get the actual album art on the discord rich presence, i am currently forced to use music presence to show the album art even tho its unreliable at best. id hope that i get an proper discord rich presence that actually works like intended and doesnt lag after songs if you switch too quickly. i know discords development documentation suggests that album art should change after 15sec but thats bogus i know other players that dont do that (they instantly change between songs/album art) without any issues.
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 victoralvesf/aonsoku, 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 victoralvesf/aonsoku acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.0% were successfully merged into the primary branch.
victoralvesf/aonsoku has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 51.1 places victoralvesf/aonsoku in the Solid tier.
The external pull request merge rate is 25.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, victoralvesf/aonsoku 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 victoralvesf/aonsoku 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.