The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for cloud-dog-egress 0.3.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 | |
|---|---|---|---|---|
| cloud_dog_egress-0.3.1.tar.gz | 30.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloud_dog_egress-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 56.2 kB
Release files / cloud_dog_egress-0.3.1.tar.gz
| Download URL | cloud_dog_egress-0.3.1.tar.gz |
|---|---|
| Size | 30.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
121a6d1a2220ca0768994a0cf7a6e786725c2c3a3f7005077e9de061be23e906
|
|
BLAKE2b-256 checksum How to use checksums |
a89d0282baf75d89c80f959937f5d3ea3357c317fad99640135bca418159bb3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / cloud_dog_egress-0.3.1-py3-none-any.whl
| Download URL | cloud_dog_egress-0.3.1-py3-none-any.whl |
|---|---|
| Size | 26.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bff3f6863fd1737857cf0aede00fb610c354ad0c8f802e5c606c02365f2b0961
|
|
BLAKE2b-256 checksum How to use checksums |
65725fb3b86d7e90891021d4e883c79b5b52b0fd7b1f2df59f0cf195dc23a231
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for cloud-dog-egress 0.3.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.
