The author of this package has not provided a project description
Metadata
Release files for specify-llm 0.0.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 | |
|---|---|---|---|---|
| specify_llm-0.0.1.tar.gz | 909 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| specify_llm-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / specify_llm-0.0.1.tar.gz
| Download URL | specify_llm-0.0.1.tar.gz |
|---|---|
| Size | 909 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c1b6c9543623b05687958139df8646cb9021a78b091b6f45410eec477753525
|
|
BLAKE2b-256 checksum How to use checksums |
7944240bd288f45cf9d1d785af370c465859975788e7be9bc72be0b1c58e5460
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Release files / specify_llm-0.0.1-py3-none-any.whl
| Download URL | specify_llm-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7bb4a845ec2e567cb406ffaa011e75b404fa1b05c4a5b47c9f826867791b53b9
|
|
BLAKE2b-256 checksum How to use checksums |
42ffde92ef2c5691f5c420941dae37488ab1ccedab87f385e9ea2d67d6259962
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Security for specify-llm 0.0.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.