2 maintainers
Metadata
2 maintainers
Release files for enkrateia 0.0.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 | |
|---|---|---|---|---|
| enkrateia-0.0.1.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| enkrateia-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / enkrateia-0.0.1.tar.gz
| Download URL | enkrateia-0.0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
147b3fb53a260eb4d359e7b27898b4d1eecc44d9a227c46d03250b04cf12a6bf
|
|
BLAKE2b-256 checksum How to use checksums |
333a1797366badbace09927fce459d55444d0d44117294bc559ac317c24cb82a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / enkrateia-0.0.1-py3-none-any.whl
| Download URL | enkrateia-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3a2ed8662cf889c6593c764cd1c8e1b99af23fa7d21401a6538b1003e942142
|
|
BLAKE2b-256 checksum How to use checksums |
af951ac70b478a04c2b6822e2ccc2fb316ed8ff045d2fea70213869581acb582
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for enkrateia 0.0.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.
