Metadata
Release files for music-library-micro 0.1.0
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_library_micro-0.1.0.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| music_library_micro-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.2 kB
Release files / music_library_micro-0.1.0.tar.gz
| Download URL | music_library_micro-0.1.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f58abe9596a44a5c660d889d683498ab5590f18c2dde7be77055c28113aa105
|
|
BLAKE2b-256 checksum How to use checksums |
eb46ae9cc3790c4cd37df42fc4c59fe54d94ae74968dd5287fdb69f72566a42a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Release files / music_library_micro-0.1.0-py3-none-any.whl
| Download URL | music_library_micro-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10e2601910685d9cf7038afcd0b50c852c180611952775fc458853e68eef1184
|
|
BLAKE2b-256 checksum How to use checksums |
20acc8fc169efb048da967dd2e2bcfdbdb93b09e2fdefc2aa86570c60b2a3021
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for music-library-micro 0.1.0
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.