Metadata
Release files for cheno 0.1.3
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 | |
|---|---|---|---|---|
| cheno-0.1.3.tar.gz | 9.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cheno-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.9 kB
Release files / cheno-0.1.3.tar.gz
| Download URL | cheno-0.1.3.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0344fe8a86deb126259d337db19e4cce67e41062c3e0d9075803eb5858e5ebc6
|
|
BLAKE2b-256 checksum How to use checksums |
6b4662a0c2a1a7fd22c364c9a559065760ba3cb104c013634af917b46764eb04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Release files / cheno-0.1.3-py3-none-any.whl
| Download URL | cheno-0.1.3-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
100be5e997ddc3f7c8b56e93297571e2f1616c64d203008ccc4dfe71c145d709
|
|
BLAKE2b-256 checksum How to use checksums |
a5bf96726d97803c0a89b4fcce8ea47a0feff833ae3feb349b65635411bf8872
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Security for cheno 0.1.3
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.