1 maintainer
Metadata
1 maintainer
Release files for basic-text-effects 0.0.4
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 | |
|---|---|---|---|---|
| basic_text_effects-0.0.4.tar.gz | 2.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| basic_text_effects-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / basic_text_effects-0.0.4.tar.gz
| Download URL | basic_text_effects-0.0.4.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d86c34b9308236cf4e15c807c254e5f4f3999965546885716ce5420e370c35d
|
|
BLAKE2b-256 checksum How to use checksums |
413018f2ba1bd8d4853f05c31ee710eddba1951ab99259b54cb2d238851a1053
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.13
|
Release files / basic_text_effects-0.0.4-py3-none-any.whl
| Download URL | basic_text_effects-0.0.4-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ef2eb33adb10458270351a5934beeaff54248834f1e6503fd4d323099dd9218
|
|
BLAKE2b-256 checksum How to use checksums |
f0645c0a4673ca76c27676e39cdc9d7f7af6bee6d64eb4b90954c03c9f024983
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.13
|
Security for basic-text-effects 0.0.4
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.
