Native TIDAL desktop client for Linux. Modern UI, custom themes, and bit-perfect lossless audio up to 24-bit/192kHz via exclusive ALSA.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 50%
Response Time: -
First Timer Success: 50%
lullabyX/sone has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lullabyX/sone 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 67.1 places lullabyX/sone in the A tier.
The external contributor pull request merge rate for lullabyX/sone is 50.0%, based on public PR activity from non-core contributors.
lullabyX/sone currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Native TIDAL desktop client for Linux. Modern UI, custom themes, and bit-perfect lossless audio up to 24-bit/192kHz via exclusive ALSA.
Strict review standards in lullabyX/sone. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in lullabyX/sone focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/lullabyX/sone?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (62% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Got an idea for SONE? Let's hear it. What's the problem you're trying to solve? I want to use SONE on mobile linux devices (e.g. with postmarketOS). The problem is that the UI doesn't exactly fit on the portrait display sizes these devices have. What would you like to see? UI should fit Anything else you've considered? There's another TIDAL app written in GTK4 (High Tide), which uses libadwaita, and is able to auto resize itself to fit on mobile displays. But I like SONE's features and functionality better :) Extra context I'm not sure which UI toolkit you're using, or if it has widgets that can resize, but GTK4 does this with libadwaita. And Qt has something similar IIUC. One last thing I had a quick look through existing issues and didn't see this one already suggested.
Got an idea for SONE? Let's hear it. What's the problem you're trying to solve? My biggest gripe switching from Spotify is, I cannot redirect playback from my desktop client to a connected device. Native mobile app supports Tidal Connect from what I can tell, but for some reason no Linux client can. What would you like to see? Extra context https://tidal.com/connect One last thing I had a quick look through existing issues and didn't see this one already suggested.
While uploaded content is playable (with some missing metadata, see: #54), it can not be browsed, if it is not added for your library via favourited album/track/playlist. Please add an option to make it available for browsing. Web client
Own uploaded songs has no lyrics/credits/suggested tracks, while in web Tidal these info are available. Tidal Hifi right: https://github.com/Mastermindzh/tidal-hifi Lyrics Credits Suggested tracks
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 lullabyX/sone, 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 lullabyX/sone acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
lullabyX/sone has a recorded first-timer success rate of 50.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 67.1 places lullabyX/sone in the Welcoming tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lullabyX/sone currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for lullabyX/sone 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.