Metadata
Release files for zeug 0.0.2
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 | |
|---|---|---|---|---|
| zeug-0.0.2.tar.gz | 2.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zeug-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.8 kB
Release files / zeug-0.0.2.tar.gz
| Download URL | zeug-0.0.2.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c892b2227da7b5238a04e19469a67753cfacac100cb9d7006517b36cf16bce8c
|
|
BLAKE2b-256 checksum How to use checksums |
b5decc37313168b62f0b159529b375f2a651e43855b6fd38b3bdf886e2e73f52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/3.7.3 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.11
|
Release files / zeug-0.0.2-py3-none-any.whl
| Download URL | zeug-0.0.2-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07118b27eef9230701a9bfed3af7a767a7bd17814709aa3b70c5bf43971b023a
|
|
BLAKE2b-256 checksum How to use checksums |
1d32c6b3bbc3904d0503b86bd063f96b1c2afa93057cf1b4e6ad747346699c41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/3.7.3 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.11
|
Security for zeug 0.0.2
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.