Metadata
Release files for meshagent-llm-proxy 0.55.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 | |
|---|---|---|---|---|
| meshagent_llm_proxy-0.55.1.tar.gz | 26.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meshagent_llm_proxy-0.55.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.3 kB
Release files / meshagent_llm_proxy-0.55.1.tar.gz
| Download URL | meshagent_llm_proxy-0.55.1.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1c9019a5752149beb4cb03665b5aae94bfd54a2aa6ad2217bdd1b9380827114
|
|
BLAKE2b-256 checksum How to use checksums |
357f1c19967508c8f8d69f2c68e7e8207edc9a3dfa54a3e5024580b7d4e79461
|
| 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.55.1-py3-none-any.whl
| Download URL | meshagent_llm_proxy-0.55.1-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b7fbec3f36c4a318bf33002acab3b6b29613b7ac4f64599fc440d5db18759f5
|
|
BLAKE2b-256 checksum How to use checksums |
45eb66c72935f26f0ec7308d7c09f012bd19351e8658f807bd4e6bd8e5fb42e9
|
| 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.55.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.