cliamp - Terminal music player inspired by winamp
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 55%
Response Time: 14h
First Timer Success: 73%
bjarneo/cliamp has a recorded first-timer success rate of 73.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bjarneo/cliamp respond to incoming external pull requests in approximately 13.7 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.4 places bjarneo/cliamp in the A tier.
The external contributor pull request merge rate for bjarneo/cliamp is 54.9%, based on public PR activity from non-core contributors.
bjarneo/cliamp currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in bjarneo/cliamp 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/bjarneo/cliamp?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (69% approval). Large PRs (>500 lines) take ~66 hours (25% approval). Keep your diff compact for rapid review.
Problem When configuring NetEase Cloud Music via cliamp setup on Windows, validation fails with: netease: validation: netease: load browser cookies: ERROR: Failed to decrypt with DPAPI. See https://github.com/yt-dlp/yt-dlp/issues/10927 for more info This is a known yt-dlp bug (yt-dlp#10927) where --cookies-from-browser fails on Windows due to DPAPI decryption issues. The issue is still open with no fix available. Currently, the NetEase provider only supports cookies_from (browser name), which maps to yt-dlp --cookies-from-browser. There is no way to use a pre-exported cookies file. Proposed solution Add a cookies_file config option as an alternative to cookies_from. When set, the provider reads cookies directly from the Netscape-format file instead of calling yt-dlp --cookies-from-browser. This serves as a workaround for the yt-dlp DPAPI issue on Windows, and is also useful for headless/CI environments where no browser is available. [netease] enabled = true cookies_file = "/path/to/co
Problem On Windows, hardware media keys do not appear to control cliamp playback. Fn + F-key should support media events produced by dedicated media keys as well as Fn/top-row media-key combinations Fn + F-key combinations Next track Previous track Pause/Play Hate having to find right terminal to pause music when I hop into a meeting.
Cliamp appears to load the first Plex library it finds, which in my case was an audiobook library rather than music. It would be great to either prompt for library selection during setup or let it be defined in the config.
Description FLAC files fail to play on Windows 11 with error: ERR: decode: ffmpeg decode: exit status 0xbebbb1b7 MP3 files play correctly on the same system. Steps to reproduce Install cliamp v1.27.8 (cliamp-windows-amd64.exe) on Windows 11 Install ffmpeg 8.1 (via winget install ffmpeg) Run cliamp.exe path/to/file.flac Expected behavior FLAC files should play normally, as ffmpeg decodes them without issues: ffmpeg -i file.flac -f wav -t 5 NUL completes successfully. Environment OS: Windows 11 Pro 10.0.26200 cliamp: v1.27.8 (cliamp-windows-amd64.exe from releases) ffmpeg: 8.1-full_build (Gyan.dev, installed via winget) FLAC files: 44100 Hz, stereo, s16
Would love to see Qobuz support as well. For reference: https://www.qobuz.com/ https://github.com/SofusA/qobuz-player
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 bjarneo/cliamp, 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 bjarneo/cliamp acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.9% were successfully merged into the primary branch.
bjarneo/cliamp has a recorded first-timer success rate of 73.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 hours. 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.4 places bjarneo/cliamp in the Welcoming tier.
The external pull request merge rate is 54.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bjarneo/cliamp currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for bjarneo/cliamp 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.