The author of this package has not provided a project description
Metadata
Release files for brainmaze-zmq 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 | |
|---|---|---|---|---|
| brainmaze-zmq-0.0.1.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brainmaze_zmq-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / brainmaze-zmq-0.0.1.tar.gz
| Download URL | brainmaze-zmq-0.0.1.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
339cd75f7719b8eb2543545edc1b2a4b6033e4abeeeac37e34cd733af972289c
|
|
BLAKE2b-256 checksum How to use checksums |
a0eb81351fcc251b1dfe8eba19063b5b8d5ac8e6e3163f62a8e2bd2736a00602
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.10
|
Release files / brainmaze_zmq-0.0.1-py3-none-any.whl
| Download URL | brainmaze_zmq-0.0.1-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8984378a9b5d92d1dbb8ae1b592202151e4e81a115e9ea4c56e32b3db807bc69
|
|
BLAKE2b-256 checksum How to use checksums |
413e1fb34c6bdc249fc26dad25118bea8807d6cd84abf0c95ecae683a9e92a95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.10
|
Security for brainmaze-zmq 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.