The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for labrador-sdk 0.0.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 | |
|---|---|---|---|---|
| labrador_sdk-0.0.2.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| labrador_sdk-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.7 kB
Release files / labrador_sdk-0.0.2.tar.gz
| Download URL | labrador_sdk-0.0.2.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
752610457c82330560adf3de831b517d81a0a9b965fbd8035b56797900c281e1
|
|
BLAKE2b-256 checksum How to use checksums |
f73de8eadc027cfb89845398a13f9fda1012d95ee9e9c9ce9b7ffcfe2f7ddc87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.3
|
Release files / labrador_sdk-0.0.2-py3-none-any.whl
| Download URL | labrador_sdk-0.0.2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
37fad8d72f85a39508cfac178d1d3469e2512aee54bb6963da44445cba5ddd7d
|
|
BLAKE2b-256 checksum How to use checksums |
bb1892a2e3b0f42fbb1a0d5133207358a90f27fe528a4fa22dbcf72d13c34ad1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.3
|
Security for labrador-sdk 0.0.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.
