For more, see the README.
Metadata
Release files for pyzenobase 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 | |
|---|---|---|---|---|
| pyzenobase-0.1.0.tar.gz | 3.9 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyzenobase-0.1.0-py3.5.egg | Legacy Egg format | - | - | Details |
| pyzenobase-0.1.0-py3.4.egg | Legacy Egg format | - | - | Details |
Total release size: 26.3 kB
Release files / pyzenobase-0.1.0.tar.gz
| Download URL | pyzenobase-0.1.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75f6cf4280443427daa98f47631290ab375a6a154420946a47bb9e8417a63c97
|
|
BLAKE2b-256 checksum How to use checksums |
5f7a47ac5a76e1225e2cb84091a501e4eaf8a81726deb7105987aa889a1bb6e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pyzenobase-0.1.0-py3.5.egg
| Download URL | pyzenobase-0.1.0-py3.5.egg |
|---|---|
| Size | 8.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
121ba70b0a81274df5a73ff9580d53fccc4dc80a15d51ccb4da4756d2bdded2c
|
|
BLAKE2b-256 checksum How to use checksums |
03a3362e70de7efc35f21811ca7294e3cadaaaca03a3f3fea1f504c165867dfd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pyzenobase-0.1.0-py3.4.egg
| Download URL | pyzenobase-0.1.0-py3.4.egg |
|---|---|
| Size | 13.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
d1d5cd07461438ea55c4173437f248cf608cdaebdd0a159344b7fd57e2165dc8
|
|
BLAKE2b-256 checksum How to use checksums |
6bffd61fe0de9c572e3cb35f8250f13f3d77fc55d5e4f5b235396468690836a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyzenobase 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.