The author of this package has not provided a project description
Metadata
Release files for llm-agregator 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 | |
|---|---|---|---|---|
| llm_agregator-0.1.0.tar.gz | 10.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llm_agregator-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.3 kB
Release files / llm_agregator-0.1.0.tar.gz
| Download URL | llm_agregator-0.1.0.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
608e13bd18c758caef3f0cc294d9405a46e897175b0caa080bc94b67dcade590
|
|
BLAKE2b-256 checksum How to use checksums |
f18b11ae6030565386222ffce6c17c6b745850a405b5fea97ddbfe21173ddb9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Release files / llm_agregator-0.1.0-py3-none-any.whl
| Download URL | llm_agregator-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21901b460c4085d39375ed60d71dbe07d7dfd8fd17f895c92a3e8d16ce6592ad
|
|
BLAKE2b-256 checksum How to use checksums |
5e32853dbd10ce53b9dcbf13e1b7c87b19f29c1241d3a286bfa056b13400da6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for llm-agregator 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.