Scrobble plays from multiple sources to multiple clients
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 100%
FoxxMD/multi-scrobbler has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in FoxxMD/multi-scrobbler 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 62.9 places FoxxMD/multi-scrobbler in the A tier.
The external contributor pull request merge rate for FoxxMD/multi-scrobbler is 72.7%, based on public PR activity from non-core contributors.
FoxxMD/multi-scrobbler currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Scrobble plays from multiple sources to multiple clients
Active TypeScript repository in FoxxMD/multi-scrobbler with ongoing community development and issue triage.
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/FoxxMD/multi-scrobbler?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 16:00 UTC (16: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 ~16 hours (91% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
Please check existing knowledge before opening an issue I have checked the documentation I have searched through existing issues and discussions. Describe the new functionality First of all, multi-scrobbler is great. I've been using it for a few years now, and I'm grateful you continue working on it. This is a follow-up to #741, which added optional position_ms support for playing_now submissions to ListenBrainz-compatible clients. I’m developing MediaWall, a Now Playing display that consumes multi-scrobbler through its ListenBrainz-compatible endpoint. One thing I want MediaWall to be able to do is remove an active session after it has been paused for a configurable number of seconds. Right now, multi-scrobbler knows when a source such as Spotify is paused internally, but that paused state is not forwarded to ListenBrainz-compatible clients. As a result, MediaWall can receive: playing_now current playback position via position_ms while playback is active, but once playback pau
Not completely sure if it's exactly the same issue, but I'm also having issues with tracking when listening to a track on repeat. Often it just seems to randomly miss some scrobbles or just scrobble it once. The thing is, it does detect that the track has been completed 6 times when looking at the source API logs, but doesn't send the scrobble. The listened percentage in Multi Scrobbler also seems correct, hitting 296% after 3 repeats and starting the 4th. The "workaround" I've discovered is to play the song in a playlist, let it finish and go to the next track for like 2 seconds and then hit previous track. This is also what you see in the second screenshot, the first 2 repeats (0:29:06 & 0:31:29) were ignored and it only send the 3rd repeat (0:34:58), which is when I started the workaround. Sometimes restarting the Spotify integration also works, as then it seems to scrobble based on the source API backlog. That seems like it gives Multi Scrobbler enough time to see the new track,
Please check existing knowledge before opening an issue I have checked the documentation I have searched through existing issues and discussions. Describe the new functionality I'd like to host multi-scrobbler on a subpage. E.g. at https://my.domain.com/multi-scrobbler. AFAICT grepping the repo, issues, and wiki, there is not a way to do this (please correct me if I'm mistaken!). To accomplish this, I'd want to run multi-scrobbler on some port and reverse proxy with caddy or nginx or similar. I worked with claude to make a few minor changes to get this to work. master...DieracDelta:multi-scrobbler:jr/multi-scrobbler. The diff is pretty small and mostly uses BASE_URL. It would probably need to be cleaned up a little bit since I've hard coded the subpath I'm using in one place (/scrobbler/). But just in case anyone else runs into this, I thought I would post here about it here. Note that I didn't test my changes with docker, but rather used a systemd service service + caddy config on
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 FoxxMD/multi-scrobbler, 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 FoxxMD/multi-scrobbler acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.7% were successfully merged into the primary branch.
FoxxMD/multi-scrobbler has a recorded first-timer success rate of 100.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 62.9 places FoxxMD/multi-scrobbler in the Welcoming tier.
The external pull request merge rate is 72.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, FoxxMD/multi-scrobbler currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for FoxxMD/multi-scrobbler 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.