llmtxt
1 maintainer
Metadata
1 maintainer
Release files for llmtxt 1.0.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 | |
|---|---|---|---|---|
| llmtxt-1.0.0.tar.gz | 505 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llmtxt-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 kB
Release files / llmtxt-1.0.0.tar.gz
| Download URL | llmtxt-1.0.0.tar.gz |
|---|---|
| Size | 505 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47ffb9094cfe51a9f9e66db07235b918ce0ce4b72e6e9b7a1452780ee6a54dfd
|
|
BLAKE2b-256 checksum How to use checksums |
8783b5c241c22499b51e5a3db8ea213c1e042599f502484ec7522d2ca1409594
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.2 CPython/3.11.4 Darwin/25.0.0
|
Release files / llmtxt-1.0.0-py3-none-any.whl
| Download URL | llmtxt-1.0.0-py3-none-any.whl |
|---|---|
| Size | 997 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
16ea1207e3811b80317fcaf1ed4d06f7776a6c2739a668743b486dc0313376f5
|
|
BLAKE2b-256 checksum How to use checksums |
1ef8b58b55513d4d2549261790ecf130f58c817b1363981f939b8dba40334d65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.2 CPython/3.11.4 Darwin/25.0.0
|
Security for llmtxt 1.0.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.
