Metadata
Release files for meshagent-llm-proxy 0.55.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.55.0.tar.gz | 26.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meshagent_llm_proxy-0.55.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.2 kB
Release files / meshagent_llm_proxy-0.55.0.tar.gz
| Download URL | meshagent_llm_proxy-0.55.0.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bce9bef27a367f63088e1e962a1481cd509e51ec61e73f630d83396ec8301048
|
|
BLAKE2b-256 checksum How to use checksums |
9ee2d2fcb36a6364a8cc88a1061b26c1aad60fb2cea3ecd92923a028f214b218
|
| 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.0-py3-none-any.whl
| Download URL | meshagent_llm_proxy-0.55.0-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa64e6def9a363420ea34773e21f80faf0c76ad7b99e86bf0bda1f8c3fafa94c
|
|
BLAKE2b-256 checksum How to use checksums |
f170485f79b6c49191f836dd52b47e8ac7c2248815bf2eec1e5c248fda0fa09a
|
| 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.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.