2 maintainers
Metadata
2 maintainers
Release files for aws-cloudtrail-tk 0.0.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 | |
|---|---|---|---|---|
| aws_cloudtrail_tk-0.0.0.tar.gz | 749 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aws_cloudtrail_tk-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / aws_cloudtrail_tk-0.0.0.tar.gz
| Download URL | aws_cloudtrail_tk-0.0.0.tar.gz |
|---|---|
| Size | 749 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf0b6047c5c965b5043d712c3b00894ee724a0520a6dab399d5a6314bd0f1254
|
|
BLAKE2b-256 checksum How to use checksums |
ae858849af6ab3fd2a9fa7145f4380211db0acb00a6b9eb9f8610cc7f1873d15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / aws_cloudtrail_tk-0.0.0-py3-none-any.whl
| Download URL | aws_cloudtrail_tk-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc73c47e31e81668553a3ac137672d245fb3e4fc86f0cf357589be1daa2f5d50
|
|
BLAKE2b-256 checksum How to use checksums |
c1bbaa01d030df9f59c354652ef308c27de6192ef8e57b0d78047128c85b8457
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for aws-cloudtrail-tk 0.0.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.
