Metadata
1 maintainer
Release files for ehn 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 | |
|---|---|---|---|---|
| ehn-0.0.0.tar.gz | 726 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ehn-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 kB
Release files / ehn-0.0.0.tar.gz
| Download URL | ehn-0.0.0.tar.gz |
|---|---|
| Size | 726 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ae198aea5d7d7637f9279874bae4ea3a4b357065d7565d7c12d7792e351936d
|
|
BLAKE2b-256 checksum How to use checksums |
2bfbac605500b9b81769e658d7dca33bde0f00b3576a2818663e323c39d33656
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.9
|
Release files / ehn-0.0.0-py3-none-any.whl
| Download URL | ehn-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc15d366b78fd7425e4fd1efda4e4292be57ea57fc5f56f75f5b98a83abcba42
|
|
BLAKE2b-256 checksum How to use checksums |
05c519e90959325a6066f725039fd3268b65d307a3f2ced717786abc38a4b358
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.9
|
Security for ehn 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.
