1 maintainer
Metadata
1 maintainer
Release files for ekspress 0.0.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 | |
|---|---|---|---|---|
| ekspress-0.0.0.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ekspress-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.1 kB
Release files / ekspress-0.0.0.tar.gz
| Download URL | ekspress-0.0.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8256dd4b882627e5d5aed94a4d7c9337b5429a0dd11e1485a76f6f19bab137d8
|
|
BLAKE2b-256 checksum How to use checksums |
9390eb0287eadbefa700681a7586ed51f373e698614910f481531bc965c6a923
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.4 Linux/5.15.90.1-microsoft-standard-WSL2
|
Release files / ekspress-0.0.0-py3-none-any.whl
| Download URL | ekspress-0.0.0-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
513a99bb6143424b84652df4055a89f3067895cbb819177d388ff5f28bc80d2c
|
|
BLAKE2b-256 checksum How to use checksums |
f272a451331cee2e22b2e292018dd961486fe5235474a7148c90bd17423fc702
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.4 Linux/5.15.90.1-microsoft-standard-WSL2
|
Security for ekspress 0.0.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.
