A modern self-hosted music player.
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 66%
Response Time: -
First Timer Success: 82%
jeffvli/feishin has a recorded first-timer success rate of 82.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jeffvli/feishin 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 64.1 places jeffvli/feishin in the A tier.
The external contributor pull request merge rate for jeffvli/feishin is 66.1%, based on public PR activity from non-core contributors.
jeffvli/feishin currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (83% positive review sentiment). Active code reviews with constructive guidance for new contributors in jeffvli/feishin.
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/jeffvli/feishin?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 Tuesday - Thursday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
I have already checked through the existing (both open AND closed) bug reports and found no duplicates Yes App Version 1.15.1 Music Server and Version Navidrome 0.63.2 What local environments are you seeing the problem on? Web Safari What happened? Web player occasionally starts two simultaneous playback streams after macOS display wake / app focus change (Safari) Steps to reproduce Play music. Switch to another fullscreen application or let the display sleep. Return to Safari / wake the display. Occasionally two different tracks are playing simultaneously. Relevant log output
I have already checked through the existing bug reports and found no duplicates Yes App Version 1.11.0 Music Server and Version Navidrome What local environments are you seeing the problem on? Desktop macOS What happened? When attempting to use MPV's audio-exclusive=yes flag on macOS while outputting to the Mac's built-in headphone jack or internal speakers, the Feishin playback UI completely freezes. The track time does not increment, no audio plays, and the app requires a hard restart (killall Feishin). The underlying cause: macOS strictly prohibits exclusive CoreAudio locks on its internal audio hardware (built-in speakers and headphone jack) to preserve system alerts. When Feishin commands mpv to take exclusive control of the BuiltInHeadphoneOutputDevice (either via the native Exclusive Mode UI toggle or via the extraParameters text box), macOS immediately denies the request and forcefully kills the mpv process. Because mpv dies instantly on startup, Feishin's background IPC bri
I have already checked through the existing bug reports and found no duplicates Yes App Version 1.1.0 Music Server and Version Jellyfin v10.11.7 What local environments are you seeing the problem on? Desktop Linux What happened? (Using the .deb file) Feishin picks up on the existing theme when the app is loaded, but doesn't not register theme changes moving forward. To change the theme, I have to manually restart Feishin or disable System Theme change Steps to reproduce Launch Feishin (will inherit current theme) Change theme Switch back to Feishin (will not change theme) Relevant log output
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 jeffvli/feishin, 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 jeffvli/feishin acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.1% were successfully merged into the primary branch.
jeffvli/feishin has a recorded first-timer success rate of 82.4%. 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 64.1 places jeffvli/feishin in the Welcoming tier.
The external pull request merge rate is 66.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jeffvli/feishin 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 jeffvli/feishin 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.