1 maintainer
Metadata
1 maintainer
Release files for evez-machine-voice 1.0.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 | |
|---|---|---|---|---|
| evez_machine_voice-1.0.0.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| evez_machine_voice-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 kB
Release files / evez_machine_voice-1.0.0.tar.gz
| Download URL | evez_machine_voice-1.0.0.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f78b7b3bdf3a22d21dbb8f7450ff58fd51f163de39e18a0720a235b27e4d7b4
|
|
BLAKE2b-256 checksum How to use checksums |
5e4e26af4c3fd14d872576f042d840c0ad23dfe987878977e061b4abef228cd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / evez_machine_voice-1.0.0-py3-none-any.whl
| Download URL | evez_machine_voice-1.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaf6a20e2910a8ba9defa339b31d1576532a2809d89efdfdabed7ec122a99628
|
|
BLAKE2b-256 checksum How to use checksums |
2b2e911759862a4ac31a96ae1ef90b0505c65a5a4404ed2e3d12c0f2f796187b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for evez-machine-voice 1.0.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.
