Metadata
Release files for meshagent-llm-proxy 0.54.2
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 | |
|---|---|---|---|---|
| meshagent_llm_proxy-0.54.2.tar.gz | 26.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meshagent_llm_proxy-0.54.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.3 kB
Release files / meshagent_llm_proxy-0.54.2.tar.gz
| Download URL | meshagent_llm_proxy-0.54.2.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9661c591689a2a0c3874ba1c9be86fdcf15681a4853677ccb8bf3b5c152c004f
|
|
BLAKE2b-256 checksum How to use checksums |
2f1b27d449659625d8b946a1bb7e782615e9919a2e5f27dae425d2237cd86726
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / meshagent_llm_proxy-0.54.2-py3-none-any.whl
| Download URL | meshagent_llm_proxy-0.54.2-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a42eeced071ab9d50e991a7b3ac78f37322e132eaf6b17c4718d5ba69c89a1ea
|
|
BLAKE2b-256 checksum How to use checksums |
d9cfa2a5f6ad131ec1917b07c44084764d92f913b13c51a4e0c13beb30379cee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for meshagent-llm-proxy 0.54.2
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.