The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for basalt-protocol 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 | |
|---|---|---|---|---|
| basalt_protocol-0.1.1.tar.gz | 3.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| basalt_protocol-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.9 kB
Release files / basalt_protocol-0.1.1.tar.gz
| Download URL | basalt_protocol-0.1.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f68b60d0627608f825c612dd8aa76115c627887794b507529c6a94e9db83796
|
|
BLAKE2b-256 checksum How to use checksums |
27293e9f57b7969e53e89766385b50e728f181a696cb743ede906dd7b9fb9d00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / basalt_protocol-0.1.1-py3-none-any.whl
| Download URL | basalt_protocol-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d96db8b4433a611541e4c3c3963997587449123c3bc80bab2eb1ecf507f5683c
|
|
BLAKE2b-256 checksum How to use checksums |
8532d3943844184ca9abdc5ec2e70b19542f1593f88b238b74616179c78ea93e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for basalt-protocol 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.
