1 maintainer
Metadata
1 maintainer
Release files for audit-trail-lib 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 | |
|---|---|---|---|---|
| audit_trail_lib-0.1.0.tar.gz | 5.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| audit_trail_lib-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.1 kB
Release files / audit_trail_lib-0.1.0.tar.gz
| Download URL | audit_trail_lib-0.1.0.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ad4053355267718fcc86dd2667ad4680bf5878be655023fa30e3653c57d1b44
|
|
BLAKE2b-256 checksum How to use checksums |
5f41ff1c0d60d17d42854fbb58787045848e0a9ee3d656753144f7389a7fe158
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / audit_trail_lib-0.1.0-py3-none-any.whl
| Download URL | audit_trail_lib-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b923108751769cb1dbccc62b1499a426e1a6b884c4c34fd6883409a147a311b
|
|
BLAKE2b-256 checksum How to use checksums |
85a53c9abec04ac34e7a8360ef0db4155dae2e0f47163d3e7a5a1a2cabb3c3df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for audit-trail-lib 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.
