multi-scrobbler

Scrobble plays from multiple sources to multiple scrobbling services.

Thriving · 82
82/100
Thriving

High commit volume, frequent releases and growing activity.

Maintenance 34/40
Releases 25/25
Community 8/20
Momentum 15/15

Commit activity more than 86% of tracked projects; popularity more than 38%. How this is calculated.

Commits, last 11 months

2025-10: 30 commits 2025-11: 92 commits 2025-12: 106 commits 2026-01: 103 commits 2026-02: 89 commits 2026-03: 154 commits 2026-04: 121 commits 2026-05: 186 commits 2026-06: 185 commits 2026-07: 237 commits 2026-08: 197 commits
2025-10 1500 total 2026-08
Stars1.2k
Latest release0.19.0 · 27 Sept 2026
Repo updated27 Sept 2026
LicenceMIT
Built withNodejs, Docker

Is multi-scrobbler actively maintained?

Over the last 11 months the project absorbed 1500 commits, of which 619 arrived in the most recent quarter — roughly 206 commits a month.

The most recent tagged release, 0.19.0, shipped within the last month — a current, installable version exists today.

Of the 28 projects we track in Media Streaming - Audio Streaming, multi-scrobbler ranks #5 by health score — in the top quarter of its category.

What multi-scrobbler actually does

Multi-scrobbler is a Node.js utility designed to listen for media playback events from various input sources and forward those records to multiple audio tracking services. It acts as an integration layer for synchronising listening history across platforms that do not natively interoperate. The project is distributed under the MIT licence and provides official container images for self-hosting.

Best fit: This is a suitable tool if you use multiple distinct audio streaming services or media players and want a unified way to report your playback history to external tracking platforms without manual intervention.

Worth knowing: You may need to manually configure API credentials, webhook endpoints, and authentication tokens for every single input and output service you wish to connect, which can introduce maintenance overhead if upstream APIs change.

Deployment notes

As a Node.js application packaged in a Docker container, it typically requires persistent storage for configuration files and database states. You will also usually want to deploy it behind a reverse proxy to handle TLS termination if any webhooks require secure HTTPS callbacks.


multi-scrobbler as a replacement for


Alternatives to multi-scrobbler

Projects in the same categories, ordered by health score.