The author of this package has not provided a project description
Metadata
Release files for authproof-py 1.6.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 | |
|---|---|---|---|---|
| authproof_py-1.6.0.tar.gz | 20.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| authproof_py-1.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.5 kB
Release files / authproof_py-1.6.0.tar.gz
| Download URL | authproof_py-1.6.0.tar.gz |
|---|---|
| Size | 20.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
342d5c6b8a926befd14276610d2a32a14e57c0e84d0b1a74ff111c041080ef0c
|
|
BLAKE2b-256 checksum How to use checksums |
924ad30fcb2c580139e2fa1c081b9e758b75ce992178ebfb9c8f99aa0830e368
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / authproof_py-1.6.0-py3-none-any.whl
| Download URL | authproof_py-1.6.0-py3-none-any.whl |
|---|---|
| Size | 24.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34e144a601a522c0c3fff7478c4c8e75179e9312afadf44116b604f5b29c6dba
|
|
BLAKE2b-256 checksum How to use checksums |
6adcb7e3505cdc5696e8e4a70951f2f2435866a8ae67bd3d1b6f8934a1de943c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for authproof-py 1.6.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.