The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for apibench 0.0.1
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 | |
|---|---|---|---|---|
| apibench-0.0.1.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apibench-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.7 kB
Release files / apibench-0.0.1.tar.gz
| Download URL | apibench-0.0.1.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c854378de4e816639578dd79243f96f53a3df4f2eaf13b2851aabe31e955301e
|
|
BLAKE2b-256 checksum How to use checksums |
905afeb7c97ed72c03fe7f94f1e5ce5be9c5ae2be5272c9f2683d5ca2c472217
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.6
|
Release files / apibench-0.0.1-py3-none-any.whl
| Download URL | apibench-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60bb1af0491bf9d2f8d5e398121afa6dae0272edc2dd19ba5ef15baaa1609a56
|
|
BLAKE2b-256 checksum How to use checksums |
6878fe50397892344e84793fa264d5bb2fdb4cf09dcc760b3c052cbffd047133
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.6
|
Security for apibench 0.0.1
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.
