Metadata
Release files for cotres 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 | |
|---|---|---|---|---|
| cotres-0.0.1.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cotres-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.5 kB
Release files / cotres-0.0.1.tar.gz
| Download URL | cotres-0.0.1.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fcf9ad51bc084e899dd5a7fd5f67e62a6ab5826eb7064ecc8e97047b17ab249
|
|
BLAKE2b-256 checksum How to use checksums |
ae28645a1fcbdfc3f29617c3dc4b9a58b180258f50c0283dd3372f2743cf7765
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.0
|
Release files / cotres-0.0.1-py3-none-any.whl
| Download URL | cotres-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e11f06620d14d3564b5d5ec866b7bcd63540209615cb95e1a635a4f15ee030be
|
|
BLAKE2b-256 checksum How to use checksums |
c101b985245758bc5b9aadeb26e7ae757b1cde2004013f73582c44bf17c2528d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.0
|
Security for cotres 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.