The author of this package has not provided a project description
Metadata
Release files for cloud-dog-db 0.3.2
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_db-0.3.2.tar.gz | 72.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloud_dog_db-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 153.7 kB
Release files / cloud_dog_db-0.3.2.tar.gz
| Download URL | cloud_dog_db-0.3.2.tar.gz |
|---|---|
| Size | 72.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d10ca1ba47d7650da8311bf1069b49071560794771985b64b3f0749b86e4c836
|
|
BLAKE2b-256 checksum How to use checksums |
4f7972f11011ca7c6d936fe88f6d512719c7b09dfdef4d1aeb032c6edde9619f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / cloud_dog_db-0.3.2-py3-none-any.whl
| Download URL | cloud_dog_db-0.3.2-py3-none-any.whl |
|---|---|
| Size | 81.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4d85e75c839b0e8de7b76de9a40801e4ea49014a7ec6075d544a98de55e4c9a
|
|
BLAKE2b-256 checksum How to use checksums |
432aaaae5cead8a3d3595da7dd4af5c0ae00e768511ac8cbcc4e4342e964fd9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for cloud-dog-db 0.3.2
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.