The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autopurix 0.1.2
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 | |
|---|---|---|---|---|
| autopurix-0.1.2.tar.gz | 10.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autopurix-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.6 kB
Release files / autopurix-0.1.2.tar.gz
| Download URL | autopurix-0.1.2.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2cfba83b382ddbde5ddf45a9f0db13de44e690a8ffd03e45f4f2820ceefdb8d9
|
|
BLAKE2b-256 checksum How to use checksums |
6c0283f104af5237a2e21800c2394834555b9b5b906deda59b47a5ba96e6ee6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Release files / autopurix-0.1.2-py3-none-any.whl
| Download URL | autopurix-0.1.2-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5af768e33137c9db6f410ac4035efc9d4c011800c0a4dfb8412b8314dc08f3b
|
|
BLAKE2b-256 checksum How to use checksums |
7bb5927fd8dfdd6f3bd5231ddddd3c68abbff264a74c20dc6a3eb8ba1f6f7b58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Security for autopurix 0.1.2
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.
