The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for hbmpC 1.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 | |
|---|---|---|---|---|
| hbmpc-1.0.0.1.tar.gz | 3.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hbmpc-1.0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.8 kB
Release files / hbmpc-1.0.0.1.tar.gz
| Download URL | hbmpc-1.0.0.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06296b7d82fff6edd0e3c35c74134da03777dddbc7af4dbbbbb8edb2192013fe
|
|
BLAKE2b-256 checksum How to use checksums |
8d434f70a267db35fa8bfe4fc85ba9d960b53249051c1e9cc327bdaa0eafd4ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / hbmpc-1.0.0.1-py3-none-any.whl
| Download URL | hbmpc-1.0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08055a5f55a635d7034c720bbe9c3c32db1518a312b06857e3644053c5de8bf6
|
|
BLAKE2b-256 checksum How to use checksums |
3200c60f782407ab67fc29dfd60dc090db67fd2d5d7b9137a1a484c2eae8a515
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for hbmpC 1.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.
