Metadata
Release files for dogu-device-client 1.2.0
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 | |
|---|---|---|---|---|
| dogu_device_client-1.2.0.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dogu_device_client-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.9 kB
Release files / dogu_device_client-1.2.0.tar.gz
| Download URL | dogu_device_client-1.2.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aec0ce5f49d297b4e1d54d99bbaf84a4836733deda93fc89e31f0a0065d2e99f
|
|
BLAKE2b-256 checksum How to use checksums |
b20486203d04f99d4f51ddb1face7f58e9ae4fb99e4c3d3ae3c02230d0f71bbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.9.13 Darwin/22.5.0
|
Release files / dogu_device_client-1.2.0-py3-none-any.whl
| Download URL | dogu_device_client-1.2.0-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a94426c465bf606179e756b3d7fdc213661b8821e90aca9129deefbb75a4c49
|
|
BLAKE2b-256 checksum How to use checksums |
09a4e6608cba5a0b1e23bc8d1b504f16812e3617ea391f94f82f491f48b2cb29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.9.13 Darwin/22.5.0
|
Security for dogu-device-client 1.2.0
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.