Metadata
Release files for music-assistant-models 1.1.227
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 | |
|---|---|---|---|---|
| music_assistant_models-1.1.227.tar.gz | 112.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| music_assistant_models-1.1.227-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 200.0 kB
Release files / music_assistant_models-1.1.227.tar.gz
| Download URL | music_assistant_models-1.1.227.tar.gz |
|---|---|
| Size | 112.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1a9682acb45906b51afed11036f4a481aac429ed146d6d8124324cc8b16040f
|
|
BLAKE2b-256 checksum How to use checksums |
b37bc76ec05ba208cda14e8d797c7ba019472cf8779b884d472e1b81954d6176
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / music_assistant_models-1.1.227-py3-none-any.whl
| Download URL | music_assistant_models-1.1.227-py3-none-any.whl |
|---|---|
| Size | 87.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e324af84ef03bdad1a28ebc3f8179fba722be0c593b16ca3c438510a8436e5bf
|
|
BLAKE2b-256 checksum How to use checksums |
340b62a0f13e1af6bed10a6222b18138ea8b90595081d694e7a91ace560afce5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for music-assistant-models 1.1.227
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.