1 maintainer
Metadata
1 maintainer
Release files for awslambdabootstrap 0.0.5
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 | |
|---|---|---|---|---|
| awslambdabootstrap-0.0.5.tar.gz | 14.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awslambdabootstrap-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.1 kB
Release files / awslambdabootstrap-0.0.5.tar.gz
| Download URL | awslambdabootstrap-0.0.5.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e0aa09962a47243472700e41b94b814164d19537c3ae7d744508546571e44f9
|
|
BLAKE2b-256 checksum How to use checksums |
e484b569c5be0f5965fd3f0e5d211e2dfed3ca1674068412143ed1553ddb6be9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.15
|
Release files / awslambdabootstrap-0.0.5-py3-none-any.whl
| Download URL | awslambdabootstrap-0.0.5-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c52d9a570cab4c34f7ffd09f5af81945387b0aecdde017a338a7791c5a5faa9f
|
|
BLAKE2b-256 checksum How to use checksums |
2e4007c510fea3f95975f66a40c62111918d07f3f8fd3168e79ad389605b20ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.15
|
Security for awslambdabootstrap 0.0.5
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.
