Metadata
Release files for topaz 0.0.3
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 | |
|---|---|---|---|---|
| topaz-0.0.3.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| topaz-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.2 kB
Release files / topaz-0.0.3.tar.gz
| Download URL | topaz-0.0.3.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f45f3d1e2cf428db45c05f318bb00290e42f28a27360b4a8b050447957047d1
|
|
BLAKE2b-256 checksum How to use checksums |
c5c7cb3f9b315c25b470af00ce9d4265d2936aacac57bb2d04bd5be56b101fba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.4
|
Release files / topaz-0.0.3-py3-none-any.whl
| Download URL | topaz-0.0.3-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
703c29ad1e3b10d6083a3c3462c33e47a9baf386f66cd6fd35c9b5e85987ad28
|
|
BLAKE2b-256 checksum How to use checksums |
ec5baa90c3b5a53863bf8b91a345e257c44122ef65a09b6155efe83de2680b3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.4
|
Security for topaz 0.0.3
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.