The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for lmbench 0.1.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 | |
|---|---|---|---|---|
| lmbench-0.1.1.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lmbench-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.5 kB
Release files / lmbench-0.1.1.tar.gz
| Download URL | lmbench-0.1.1.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8375e159a264c3a362112a8eb04dfeb5b0afcd1ecb9ec77c2d0b05b3f4d051fe
|
|
BLAKE2b-256 checksum How to use checksums |
1f167e81ffd506048a8a65dfaf2e4f431a1de1859da3cb211bf6a40f21a63aed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / lmbench-0.1.1-py3-none-any.whl
| Download URL | lmbench-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11985b732fabe0d8132f12f67f9c37f890676a42384225e09057ec2fcfe60ca4
|
|
BLAKE2b-256 checksum How to use checksums |
9e5da127ff0afacf02a8e5755898e133968d54dd6280cd9aaa4a38034b8290b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for lmbench 0.1.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.
