The author of this package has not provided a project description
Metadata
Release files for cloud-dog-config 0.3.4
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_config-0.3.4.tar.gz | 81.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloud_dog_config-0.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 149.5 kB
Release files / cloud_dog_config-0.3.4.tar.gz
| Download URL | cloud_dog_config-0.3.4.tar.gz |
|---|---|
| Size | 81.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
017b73e8b2fbb1fceffb9025a93815668930339f13cd554e63b2373a1e44f7b9
|
|
BLAKE2b-256 checksum How to use checksums |
15482c0c9b4d46404007b8353b95c12fdfaea5fd9d1a23d82c02a572947dce43
|
| 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_config-0.3.4-py3-none-any.whl
| Download URL | cloud_dog_config-0.3.4-py3-none-any.whl |
|---|---|
| Size | 67.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1cebbe9af173bcb177165966df255607cca8edcfc4f6315ecfd1548b55589b3
|
|
BLAKE2b-256 checksum How to use checksums |
98fe39dccfd8291067cca4a229d188a259a30e345e8db6736be6c1a022d9cd9c
|
| 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-config 0.3.4
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.