The author of this package has not provided a project description
Metadata
Release files for aws-noaction 0.1.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_noaction-0.1.1.tar.gz | 1.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aws_noaction-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.1 kB
Release files / aws_noaction-0.1.1.tar.gz
| Download URL | aws_noaction-0.1.1.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2e4212bc4e9c0bfea02ed0d3be68ab60fffcd2faccbabafd11cfac78b0ad373
|
|
BLAKE2b-256 checksum How to use checksums |
613da051071f28f0ec80bd1dc2b9a3904ec793bf23c58e7fb782fc61dd54da81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.12
|
Release files / aws_noaction-0.1.1-py3-none-any.whl
| Download URL | aws_noaction-0.1.1-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5051b91c35a9812ff391c2ab7131c7079a91668a05f0ef34c9bdc114ede1356
|
|
BLAKE2b-256 checksum How to use checksums |
fc96ac979f06f0b868099ccbdd41cd3f5a5d270c90a258d9f088705c9e02c89f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.10.12
|
Security for aws-noaction 0.1.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.