mopidy-scrobbler
Mopidy extension for scrobbling played tracks to Last.fm or Libre.fm.
This extension requires a free user account at Last.fm or Libre.fm.
Maintainer wanted
Mopidy-Scrobbler is currently kept on life support by the Mopidy core developers. It is in need of a more dedicated maintainer.
If you want to be the maintainer of Mopidy-Scrobbler, please:
-
Make 2-3 good pull requests improving any part of the project.
-
Read and get familiar with all of the project's open issues.
-
Send a pull request removing this section and adding yourself as the "Current maintainer" in the "Credits" section below. In the pull request description, please refer to the previous pull requests and state that you've familiarized yourself with the open issues.
As a maintainer, you'll be given push access to the repo and the authority to make releases to PyPI when you see fit.
Installation
Install by running:
python3 -m pip install mopidy-scrobbler
See https://mopidy.com/ext/scrobbler/ for alternative installation methods.
Configuration
The extension is enabled by default when it is installed. You just need to add your Last.fm username and password to your Mopidy configuration file:
[scrobbler]
username = my-last.fm-username
password = my-last.fm-password
To use Libre.fm instead, you must specify the network too:
[scrobbler]
network = librefm
username = my-libre.fm-username
password = my-libre.fm-password
The following configuration values are available:
scrobbler/enabled: If the scrobbler extension should be enabled or not. Defaults to enabled.scrobbler/network: The scrobbling network to use. Can be eitherlastfmorlibrefm. Defaults tolastfm.scrobbler/username: Your Last.fm or Libre.fm username.scrobbler/password: Your Last.fm or Libre.fm password.
Project resources
Development
Set up development environment
Clone the repo using, e.g. using gh:
gh repo clone mopidy/mopidy-scrobbler
Enter the directory, and install dependencies using uv:
cd mopidy-scrobbler/
uv sync
Running tests
To run all tests and linters in isolated environments, use tox:
tox
To only run tests, use pytest:
pytest
To format the code, use ruff:
ruff format .
To check for lints with ruff, run:
ruff check .
To check for type errors, use pyright:
pyright .
Making a release
To make a release to PyPI, go to the project's GitHub releases page and click the "Draft a new release" button.
In the "choose a tag" dropdown, select the tag you want to release or create a
new tag, e.g. v0.1.0. Add a title, e.g. v0.1.0, and a description of the changes.
Decide if the release is a pre-release (alpha, beta, or release candidate) or should be marked as the latest release, and click "Publish release".
Once the release is created, the release.yml GitHub Action will automatically
build and publish the release to
PyPI.
Credits
- Original author: Stein Magnus Jodal
- Current maintainer: None. Maintainer wanted, see section above.
- Contributors
Metadata
Release files for mopidy-scrobbler 3.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mopidy_scrobbler-3.1.1.tar.gz | 14.1 kB | With provenance | Details for mopidy_scrobbler-3.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mopidy_scrobbler-3.1.1-py3-none-any.whl | Python 3 | none | any | Details for mopidy_scrobbler-3.1.1-py3-none-any.whl |
Total release size: 24.4 kB
Release files / mopidy_scrobbler-3.1.1.tar.gz
| Download URL | mopidy_scrobbler-3.1.1.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03af6d203784627e85ced3ad0670e45ff0a4b07a2ba51da0b8d105c1b845b78f
|
|
BLAKE2b-256 checksum How to use checksums |
8f5f1fff221adf0c7d1b378896ae1ba472efde736ccdae2febec3b4fcac9b0ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / mopidy_scrobbler-3.1.1-py3-none-any.whl
| Download URL | mopidy_scrobbler-3.1.1-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2555fe52e38416c90ada9063722e0ceb639b00a3c84b0c22aec88e56a5bc0b4
|
|
BLAKE2b-256 checksum How to use checksums |
6e95c43c0050091f43f16cc464b0af80406db04bb83e24dca27f5fa9782fd4da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logSecurity for mopidy-scrobbler 3.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mopidy_scrobbler-3.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.