The author of this package has not provided a project description
Metadata
Release files for cloud-dog-db 0.3.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 | |
|---|---|---|---|---|
| cloud_dog_db-0.3.3.tar.gz | 80.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloud_dog_db-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 169.1 kB
Release files / cloud_dog_db-0.3.3.tar.gz
| Download URL | cloud_dog_db-0.3.3.tar.gz |
|---|---|
| Size | 80.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4f6b72d37a460cbd8c857419108de4edabda204480ea30916181f10fecc4404
|
|
BLAKE2b-256 checksum How to use checksums |
0688f1ec38d6780479fbc6f0a929c98cbe67472ca9535bcc90b2e65bae973791
|
| 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_db-0.3.3-py3-none-any.whl
| Download URL | cloud_dog_db-0.3.3-py3-none-any.whl |
|---|---|
| Size | 89.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0694dce0bc325c60fa7e93a3d42aa6b394fcd61448468ada069e75d67d6544eb
|
|
BLAKE2b-256 checksum How to use checksums |
ced6f5b18460411558c541f5d17ac3503c60ea6f05a42bd11e6ffa33eff8c8d8
|
| 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-db 0.3.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.