The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for AutoTTS 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 | |
|---|---|---|---|---|
| autotts-0.1.0.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autotts-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.9 kB
Release files / autotts-0.1.0.tar.gz
| Download URL | autotts-0.1.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05b8771a00399cf655e26dac7685a5151b758d93c3f8c236c084b6fa330d7685
|
|
BLAKE2b-256 checksum How to use checksums |
1d733857852c20cc43cbd5dd73a54dca5b274e7d9a119408cfccbfafb6ac5c81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Release files / autotts-0.1.0-py3-none-any.whl
| Download URL | autotts-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c80dfe04bc8bf41858e4b08f45e51964c3d02d55972a66daa47c88785cefb85
|
|
BLAKE2b-256 checksum How to use checksums |
18c6a5486f46261526c6fa3694d7f49e14af1ddeb41716a4fab0f7d8a79e9b6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.9
|
Security for AutoTTS 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.
