The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dzen 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 | |
|---|---|---|---|---|
| dzen-0.1.0.tar.gz | 765 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dzen-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 kB
Release files / dzen-0.1.0.tar.gz
| Download URL | dzen-0.1.0.tar.gz |
|---|---|
| Size | 765 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b40aac130bc9342327ecf034cd8974df3153664d91940ca254c1c93468e5b429
|
|
BLAKE2b-256 checksum How to use checksums |
b40cd26e652ab0eea3c29d4bb72b49abb3e3697a5c849589b82c01366856a611
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.17 CPython/3.8.0 Darwin/19.2.0
|
Release files / dzen-0.1.0-py3-none-any.whl
| Download URL | dzen-0.1.0-py3-none-any.whl |
|---|---|
| Size | 966 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d9723bf185cceb237cfc9e02335abf3a0f605845af6fab3e6e41d49978c0474
|
|
BLAKE2b-256 checksum How to use checksums |
bbaf4e7978369c9911390da7cd56293254c2064758afca47412208c314a958ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.17 CPython/3.8.0 Darwin/19.2.0
|
Security for dzen 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.
