Metadata
Release files for blockdiagcontrib-eps 0.1.1
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 | |
|---|---|---|---|---|
| blockdiagcontrib-eps-0.1.1.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blockdiagcontrib_eps-0.1.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 11.1 kB
Release files / blockdiagcontrib-eps-0.1.1.tar.gz
| Download URL | blockdiagcontrib-eps-0.1.1.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0640b8ebfe7c20e5001f77116fe7894c9a6c7786c992487901109dec00c77d21
|
|
BLAKE2b-256 checksum How to use checksums |
1a69e6f0323b4aafe6b351d3117f78117147260281caef0608664112dfd1b070
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / blockdiagcontrib_eps-0.1.1-py2.py3-none-any.whl
| Download URL | blockdiagcontrib_eps-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
abbdfae5f61e98f70b82af298ed4d9f0426176d0a3176784275b83c7a967c061
|
|
BLAKE2b-256 checksum How to use checksums |
3faa7f6192fc2cabd44487c45062e2d9a0f5d5494edc507c3c2f81415f936a10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for blockdiagcontrib-eps 0.1.1
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.