The author of this package has not provided a project description
Metadata
Release files for latch-sdk-config 0.0.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 | |
|---|---|---|---|---|
| latch-sdk-config-0.0.4.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| latch_sdk_config-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.3 kB
Release files / latch-sdk-config-0.0.4.tar.gz
| Download URL | latch-sdk-config-0.0.4.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72bfec47364abce7f6096d794fe3ebed29c4cb1aafb60adc4438fca15ddea15d
|
|
BLAKE2b-256 checksum How to use checksums |
e7ae3597280830ca310569554daeee252cd597894407986529fb44f00fb46646
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.0
|
Release files / latch_sdk_config-0.0.4-py3-none-any.whl
| Download URL | latch_sdk_config-0.0.4-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f4d9dd7f5d7cda65ab96557a0792b910886bf7f1b6bd36b722d89df9b610609
|
|
BLAKE2b-256 checksum How to use checksums |
13e472725cedb6770af45bfae52804b37b4b1db6aed687137a7f3a1de5427514
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.0
|
Security for latch-sdk-config 0.0.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.