2 maintainers
Metadata
2 maintainers
Release files for listening-machine 0.0.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 | |
|---|---|---|---|---|
| listening_machine-0.0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| listening_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 kB
Release files / listening_machine-0.0.1.tar.gz
| Download URL | listening_machine-0.0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a06e7dd4f392a0f7cded285ffeb61c172d0e45f70d74548a163d6e7aad98738c
|
|
BLAKE2b-256 checksum How to use checksums |
db41607bcd724fff6533db0d57a1e2e502a544721973e017bdcdefd0dc327bc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / listening_machine-0.0.1-py3-none-any.whl
| Download URL | listening_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ff132a03966c94d0e79e2c9ce7c80556861a59f6b5694560dcb80d4509b6426d
|
|
BLAKE2b-256 checksum How to use checksums |
2c9e99fb91f85cd7a3c2093fbe1697e0f90f4ca287b7ddeda0c971f8b347b355
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for listening-machine 0.0.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.
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.
