The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for afriverify 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 | |
|---|---|---|---|---|
| afriverify-0.1.0.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| afriverify-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.3 kB
Release files / afriverify-0.1.0.tar.gz
| Download URL | afriverify-0.1.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47e4153b445e0421726ace38292b944e0410ec6cdf448a3ca42158e70c5eb04c
|
|
BLAKE2b-256 checksum How to use checksums |
a0b1efbb557849ab28915108c1a17551441bf0647ec16696f8beb1d0c0fef031
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / afriverify-0.1.0-py3-none-any.whl
| Download URL | afriverify-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22e51fda36eb271612c91cbcf199e3e8f9af743c03e67de35fc16ead32d9343e
|
|
BLAKE2b-256 checksum How to use checksums |
6be5fa81e1ffd5c8cba88e01fc1027efa9263e0df2cb616c6424b2949361d33c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Security for afriverify 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.
