The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for jbmpC 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 | |
|---|---|---|---|---|
| jbmpc-1.0.0.1.tar.gz | 3.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jbmpc-1.0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.7 kB
Release files / jbmpc-1.0.0.1.tar.gz
| Download URL | jbmpc-1.0.0.1.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48e9cc8b6e1395c33482e1817fa5548855a100f25782a38318ec4dcfdc54e098
|
|
BLAKE2b-256 checksum How to use checksums |
a1b3ce06416e51225d32188a079c917ac967d0ed26b7832e07dc9c495994dff4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / jbmpc-1.0.0.1-py3-none-any.whl
| Download URL | jbmpc-1.0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
daeb64cb35d8d68a5379c2f7f4d18cca660e7e533a773ba8c6dbfcd8369b83ea
|
|
BLAKE2b-256 checksum How to use checksums |
a011dc6e46f05fd691f3389671f662d471675f2936bea539b751aa947271ab8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for jbmpC 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.
