🎵 Cross-platform desktop music player with rich lyric support and wide audio format compatibility. 跨平台桌面音乐播放器，支持丰富歌词与多种音频格式
C-Rank Grade: A (Welcoming) - 55/100
External PR Merge Rate: 45%
Response Time: -
First Timer Success: 29%
SPlayer-Dev/SPlayer-Next has a recorded first-timer success rate of 28.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in SPlayer-Dev/SPlayer-Next 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 54.8 places SPlayer-Dev/SPlayer-Next in the A tier.
The external contributor pull request merge rate for SPlayer-Dev/SPlayer-Next is 44.7%, based on public PR activity from non-core contributors.
SPlayer-Dev/SPlayer-Next currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
🎵 Cross-platform desktop music player with rich lyric support and wide audio format compatibility. 跨平台桌面音乐播放器，支持丰富歌词与多种音频格式
Active maintainer team in SPlayer-Dev/SPlayer-Next 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/SPlayer-Dev/SPlayer-Next?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (56% approval). Large PRs (>500 lines) take ~115 hours (20% approval). Keep your diff compact for rapid review.
检查清单 我已检索仓库中所有的 Issues，确保我没有重复提交问题；或有相似 Issue，但我觉得我的情况不包含在那个相似 Issue 之内 我已经找到了可以复现这个问题的方法，并且写在了下面的「具体信息」中 此问题可以在我的设备和当前环境中稳定复现 此问题可以在最新版本 (Latest Release) 中复现 此问题是在我更新到当前版本后才出现的 当前系统环境 Windows 11 25H2 (OS 内部版本 26200.8973) 当前版本 0900e25 具体信息 前提：开启任务栏歌词 复现： 在歌曲播放期间，触发 explorer.exe 重启行为 SPlayer-Next 首先会无响应，随后闪退 感觉跟 explorer.exe 的监听有关吧，日志看着挺正常的 2026-08-15.log 不管怎么样，SPlayer-Next 真的好优雅😋
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 SPlayer-Dev/SPlayer-Next, 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 SPlayer-Dev/SPlayer-Next acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 44.7% were successfully merged into the primary branch.
SPlayer-Dev/SPlayer-Next has a recorded first-timer success rate of 28.6%. 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 54.8 places SPlayer-Dev/SPlayer-Next in the Welcoming tier.
The external pull request merge rate is 44.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, SPlayer-Dev/SPlayer-Next 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 SPlayer-Dev/SPlayer-Next 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.