1 maintainer
Metadata
1 maintainer
Release files for arcapprove-bendex 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 | |
|---|---|---|---|---|
| arcapprove_bendex-0.1.0.tar.gz | 6.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arcapprove_bendex-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.9 kB
Release files / arcapprove_bendex-0.1.0.tar.gz
| Download URL | arcapprove_bendex-0.1.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7763c2cb0c66c38dae80203c271d0a18cc9bb3fae2cda8a04c2699680c6b7812
|
|
BLAKE2b-256 checksum How to use checksums |
f84ad07bbb275d3007c322fd521ed75ac140c2fb428a7e01be45164a0a68510c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / arcapprove_bendex-0.1.0-py3-none-any.whl
| Download URL | arcapprove_bendex-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51c372d9370d307bd5fd104138b5ce10839e878d1b9b607ab2c8a3ec11b5436a
|
|
BLAKE2b-256 checksum How to use checksums |
c2b2f1f9756097b3be0ef0e14f75ad1f11b07c422eb9fe1995f9f1053b99a225
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for arcapprove-bendex 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.
