The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for chalice-cdk 0.1.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 | |
|---|---|---|---|---|
| chalice-cdk-0.1.0.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chalice_cdk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / chalice-cdk-0.1.0.tar.gz
| Download URL | chalice-cdk-0.1.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a21d3c841c7ca02dafcbcf0b4226d2154c1b8272dabc0c2aa89ff508b861f5a2
|
|
BLAKE2b-256 checksum How to use checksums |
679e67f5b37f1f57dc023ca3a9671257ecf864e9e53b66d91dcc7e101a5e52a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.7.7 Darwin/19.5.0
|
Release files / chalice_cdk-0.1.0-py3-none-any.whl
| Download URL | chalice_cdk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99415c70126627bf10456a0f284c9037facfd8717f5e320ff42a5d389e8c0d08
|
|
BLAKE2b-256 checksum How to use checksums |
7bc0d7692400107c91ac5bb40f1157093b25f9472871b9f66cf4b57313e525a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.7.7 Darwin/19.5.0
|
Security for chalice-cdk 0.1.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.
