1 maintainer
Metadata
1 maintainer
Release files for bcache-tools 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 | |
|---|---|---|---|---|
| bcache-tools-0.1.tar.gz | 14.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bcache_tools-0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 30.8 kB
Release files / bcache-tools-0.1.tar.gz
| Download URL | bcache-tools-0.1.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd53da2a9142ddc95529853317f71e371a3bac54dc5696de399331238b0997b4
|
|
BLAKE2b-256 checksum How to use checksums |
f4c9381be9cea0b849946ad9e94ebb4980626ddcc669df78e3fab193ff5bea54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / bcache_tools-0.1-py2.py3-none-any.whl
| Download URL | bcache_tools-0.1-py2.py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
dc9a5ab9178c77e4c78d5a6aee7b0ec11f71506443c7f0ac8cbc762926f68344
|
|
BLAKE2b-256 checksum How to use checksums |
153c48f47623dd503e46c6e60094656746c3219eefc8d2b0bd6e0aa8cedddc2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for bcache-tools 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.
