1 maintainer
Metadata
1 maintainer
Release files for beacon-protocol-sdk 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 | |
|---|---|---|---|---|
| beacon_protocol_sdk-0.1.1.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beacon_protocol_sdk-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.4 kB
Release files / beacon_protocol_sdk-0.1.1.tar.gz
| Download URL | beacon_protocol_sdk-0.1.1.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63c3716268c042c561615532e3795fe98ceed6ce0bb4fd89de640449ed14f4ca
|
|
BLAKE2b-256 checksum How to use checksums |
022e8b5be86357a642a7a4fa30a5b65a1529c33901a35d7459e0205145fc4ed1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / beacon_protocol_sdk-0.1.1-py3-none-any.whl
| Download URL | beacon_protocol_sdk-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e7ca05ba184042e70aad3aa59b0256c12f8a12c4957e306cd7c07b54480c3505
|
|
BLAKE2b-256 checksum How to use checksums |
d7ced56bdeb803523d256f77c2311b5a7e8cd819cfbd39c809ad8340e701acb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for beacon-protocol-sdk 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.
