The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for rmq-client 0.1.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 | |
|---|---|---|---|---|
| rmq_client-0.1.0.tar.gz | 8.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rmq_client-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.8 kB
Release files / rmq_client-0.1.0.tar.gz
| Download URL | rmq_client-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f0a4acf3671d1026fc180286f03a43b6adcbec82da9832fb7faf3bb1592bba2
|
|
BLAKE2b-256 checksum How to use checksums |
ed5d029ad5375b7745d8b4ebc44d657097e2b2917ff3762fe83e8e1264d13665
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.10
|
Release files / rmq_client-0.1.0-py3-none-any.whl
| Download URL | rmq_client-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fee6645bf333d4ce4ede02ac9b4aa6fa54d2ad522a7a7e730c55884944dadf24
|
|
BLAKE2b-256 checksum How to use checksums |
2efea304f9243ae2f64ca80c7834ed7b8cdfccad85192abd9de82aa17274ba05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.10
|
Security for rmq-client 0.1.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.
