The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for awslake 1.1.17
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 | |
|---|---|---|---|---|
| awslake-1.1.17.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awslake-1.1.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.1 kB
Release files / awslake-1.1.17.tar.gz
| Download URL | awslake-1.1.17.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a575b96eabc402cc867671eb17ea8e5ff7d88c1f141b825a9e029323c29aa06e
|
|
BLAKE2b-256 checksum How to use checksums |
905d6eebb48fbe55c183b50fbb0433214fa56e289bc7e78d8d91f1e336517933
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.7
|
Release files / awslake-1.1.17-py3-none-any.whl
| Download URL | awslake-1.1.17-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a44e562408f08e7cad01f95a5d5f16833ad9a77f9867c4c18e8755dca80e4776
|
|
BLAKE2b-256 checksum How to use checksums |
270745f80f5a1202a395a8cdd4f87faf10986396b467a69358097365de1261c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.7
|
Security for awslake 1.1.17
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.
