driftwatch-llm
Command-line tool for DriftWatch, a drift monitor for LLM apps.
Status: early. This release only links a project folder to your DriftWatch account:
pip install driftwatch-llm
driftwatch init # sign in through your browser and link this folder to a project
driftwatch status
driftwatch logout
It does not monitor anything yet. The background agent and the local dashboard come in later releases.
What it stores on your machine: one project API key in your OS keychain (or a private file if no
keychain exists), a trust record, and .driftwatch/config.toml in your project folder, which holds a
project id and nothing else. Installing the package changes nothing; only the commands above do.
MIT licensed.
Metadata
Release files for driftwatch-llm 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 | Actions |
|---|---|---|---|---|
| driftwatch_llm-0.1.0.tar.gz | 14.0 kB | With provenance | Details for driftwatch_llm-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| driftwatch_llm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for driftwatch_llm-0.1.0-py3-none-any.whl |
Total release size: 33.6 kB
Release files / driftwatch_llm-0.1.0.tar.gz
| Download URL | driftwatch_llm-0.1.0.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a5d9471f8808c5b28c3fe130018e37eacba064ccbd5be4034cc720b8734dc07
|
|
BLAKE2b-256 checksum How to use checksums |
b3d1095645f3fff5da7227abdb91f5743eea4c991933ea627b7823b9203c65c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / driftwatch_llm-0.1.0-py3-none-any.whl
| Download URL | driftwatch_llm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a7b78e60f1553bd12097b468dc48823ce8749819fc7fa51adabf738c7c17061
|
|
BLAKE2b-256 checksum How to use checksums |
dc5bdb3fd9287e6fc7501e7c35ba4a626a1de3118517458ffd69aad52ad8c8ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logSecurity for driftwatch-llm 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for driftwatch_llm-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.