This release is a pre-release and may not be stable for production use.
Metadata
Release files for auditicy 0.0.1a2
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 | |
|---|---|---|---|---|
| auditicy-0.0.1a2.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auditicy-0.0.1a2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.5 kB
Release files / auditicy-0.0.1a2.tar.gz
| Download URL | auditicy-0.0.1a2.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc4dfffe94b32bbc38e7314e6fa2982d3d8d91dccc4be264911972ad54903a90
|
|
BLAKE2b-256 checksum How to use checksums |
54bf57233cae762d59b27436cb1522311b5f7688dd53ea8224f738a3c8e71209
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.10
|
Release files / auditicy-0.0.1a2-py3-none-any.whl
| Download URL | auditicy-0.0.1a2-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e034d6f6be894f55bf87b69cc2d7409511b10353f033e362fe3b834637b83570
|
|
BLAKE2b-256 checksum How to use checksums |
94636e3ec714678f1d8eb74d441fca586c701586fa164bee946ccfeb3d104f35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.10
|
Security for auditicy 0.0.1a2
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.