Metadata
1 maintainer
Release files for aws-message-client 1.6.1
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 | |
|---|---|---|---|---|
| aws_message_client-1.6.1.tar.gz | 14.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aws_message_client-1.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.0 kB
Release files / aws_message_client-1.6.1.tar.gz
| Download URL | aws_message_client-1.6.1.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8449277ac973c9dc84dc3600559648dedbec68365e612f850e44ef611de2807
|
|
BLAKE2b-256 checksum How to use checksums |
4ba1b8b105e506ac97702e67e060d50b811d9bfde4e20713b9a2c883c3294536
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / aws_message_client-1.6.1-py3-none-any.whl
| Download URL | aws_message_client-1.6.1-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5740aeff05f950d090216ba889880783c36152b3e1f44c807cb9ab991d610990
|
|
BLAKE2b-256 checksum How to use checksums |
351948b69c9a350a2f2387e15cde62364e8404082f5b085d2028ef0a61cad28c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for aws-message-client 1.6.1
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.
