Official Android App of ListenBrainz
C-Rank Grade: B (Solid) - 43/100
External PR Merge Rate: 75%
Response Time: 17d
First Timer Success: 100%
metabrainz/listenbrainz-android 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 metabrainz/listenbrainz-android respond to incoming external pull requests in approximately 407.8 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 42.6 places metabrainz/listenbrainz-android in the B tier.
The external contributor pull request merge rate for metabrainz/listenbrainz-android is 75.0%, based on public PR activity from non-core contributors.
metabrainz/listenbrainz-android currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in metabrainz/listenbrainz-android 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/metabrainz/listenbrainz-android?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 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~265 hours (94% approval). Large PRs (>500 lines) take ~1957 hours (34% approval). Keep your diff compact for rapid review.
Steps to Reproduce: Open ListenBrainz App Switch to landscape mode Go to profile screen tap on created for you or artist screen App crashes immediately Expected Behavior: It should open the respective screens Environment: Android Version: 16 App Version: 2.15.1.0 Device: Motorolla g86 Power Screen Recording: WhatsApp.Video.2026-04-05.at.11.48.11.PM.mp4
User feedback on current state of profile screens Stats tab. https://www.reddit.com/r/listenbrainz/comments/1r6zvj2/i_really_love_the_website_stats_feature_i_would/ Majorly: Loading, success and failure states. Interactions with graph. Majorly, we need to compare the page with website side by side to align web and app.
I find the idea of using the ListenBrainz player more and more interesting, and how I would mostly interact with such is a homescreen widget. LineageOS eleven music player provided a nice widget with title/artist/album metadata, as well as cover, and controls for play/pause, and skip back/next, as well as repeat and shuffle. Having it resident and exempted from battery management meant I could easily play my music from the widget without diving into menus, and would auto pause/resume when entering/leaving my car, for instance. Not running both a player and scrobbler is kinder on the battery and limited system resources. One could even add controls for heart, driving the ListenBrainz algo development even more easily.
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 metabrainz/listenbrainz-android, 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 metabrainz/listenbrainz-android acknowledge new external contributions in approximately 16 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.
metabrainz/listenbrainz-android 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 ~16 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 42.6 places metabrainz/listenbrainz-android in the Solid tier.
The external pull request merge rate is 75.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, metabrainz/listenbrainz-android 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 metabrainz/listenbrainz-android 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.