Metadata
Release files for meshagent-llm-proxy 0.54.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 | |
|---|---|---|---|---|
| meshagent_llm_proxy-0.54.0.tar.gz | 26.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meshagent_llm_proxy-0.54.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.3 kB
Release files / meshagent_llm_proxy-0.54.0.tar.gz
| Download URL | meshagent_llm_proxy-0.54.0.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bb23c90a09d24928d0b291f3376c264f6365a804d8d2a7a17c63d3137b8ef5df
|
|
BLAKE2b-256 checksum How to use checksums |
049634ddcccef54e85d65b1dcea7c92a4b5e6d64fe72ce3f9a8882152c7e59e3
|
| 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.0-py3-none-any.whl
| Download URL | meshagent_llm_proxy-0.54.0-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f55e94e119e0e4ad1aba401eca84a5d141edaec6457d396374eed9833f582cc4
|
|
BLAKE2b-256 checksum How to use checksums |
de26518e92dad578b086821c6ae6f820d9054b2e285db0ca551b24d32d21953a
|
| 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.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.