Metadata
Release files for pydecon 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 | |
|---|---|---|---|---|
| pydecon-0.0.1.tar.gz | 34.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pydecon-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.9 kB
Release files / pydecon-0.0.1.tar.gz
| Download URL | pydecon-0.0.1.tar.gz |
|---|---|
| Size | 34.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa623399b863a8bebce54fea24d95522e9e946489412dbc8b20104f22a2042ca
|
|
BLAKE2b-256 checksum How to use checksums |
e62dcf86ee73110876527d0f3f6cb54e5b8283f6a9793f6fba2a3b743e6d8286
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/53.0.0 requests-toolbelt/0.9.1 tqdm/4.56.2 CPython/3.9.1
|
Release files / pydecon-0.0.1-py3-none-any.whl
| Download URL | pydecon-0.0.1-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23f085a2728035bcbba3521718b6bd98325af8e0556387c06dec29e6a079605f
|
|
BLAKE2b-256 checksum How to use checksums |
db8fa6ae151b2c6ab62e15d0dede354554bc3bfb408a710cacda0c1d22c9dab3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/53.0.0 requests-toolbelt/0.9.1 tqdm/4.56.2 CPython/3.9.1
|
Security for pydecon 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.