Metadata
Release files for chp-adapter-messages 0.28.0
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 | |
|---|---|---|---|---|
| chp_adapter_messages-0.28.0.tar.gz | 6.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chp_adapter_messages-0.28.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / chp_adapter_messages-0.28.0.tar.gz
| Download URL | chp_adapter_messages-0.28.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a196e05de36173cd000dcb31870bb2fa5c7229bbfc5624e43b64f66fff32eb8
|
|
BLAKE2b-256 checksum How to use checksums |
b3607c7f6aba81f0ffc11fca866ddc4f1907ab9232f305e64299ac469ab655db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Release files / chp_adapter_messages-0.28.0-py3-none-any.whl
| Download URL | chp_adapter_messages-0.28.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d965f2556f0b4a4c78c275470ce3e14440fe8cca5fc8f6dc9c7a5e8f85317d91
|
|
BLAKE2b-256 checksum How to use checksums |
58cc4e2d378b45a2bb5d03888c62d619ff5bed8de4b471b012c4b5dd274784df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Security for chp-adapter-messages 0.28.0
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.