assurance-cli
Did the job cover everything it was supposed to cover? Arithmetic, not models.
Install
pip install assurance-cli
# or: pip install assurance # every tool
Quick start
assurance --help lists: init, check, diff, pin, drift, deps, budget, authority, audit.
audit, budget, authority, and deps forward to their packages when installed.
Point check at a folder of dated files (real output from a temp folder with Jan, Feb, Apr CSVs):
$ assurance check reports
3 of 4 months from 2026-01 to 2026-04 in reports — not in this folder: March 2026 — Range inferred from filenames: earliest 2026-01, latest 2026-04 — uneven spacing, so monthly was read from the names rather than detected. Override with --expect / --from / --to.
With --fail-on-gap that same line exits 1.
diff compares any two sets of keys (no folder required). pin snapshots MCP tool definitions and detects drift. drift watches a binary outcome stream.
What it checks
- Dated or numbered series in a folder (
check) — months, weeks, days, numbered runs - Coverage over any two key sets (
diff) - MCP tool-description drift since a pin (
pin) - Shift in a binary outcome stream (
drift) - Forwards: session audit, run budget, authority review, dependency install hooks
In CI
| exit | means |
|---|---|
0 |
checked; no gap (or not asked to fail on one) |
1 |
gap / unexpected key / stale pin / nothing it could check |
2 |
could not run (bad path, missing sibling package, bad JSON) |
Limits
- Does not invent the expected set.
difftakes your declaration;checkderives one and prints how. - No network, no telemetry, no keys.
- A folder it cannot parse exits 1, not 0 — silence is not a pass.
- Skipped tool directories (
.git,node_modules, …) are named, not folded into “files not opened” as if they were content.
See the root README and CHANGELOG.md.
1 maintainer
Release files for assurance-cli 0.6.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 | |
|---|---|---|---|
| assurance_cli-0.6.1.tar.gz | 68.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| assurance_cli-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 116.0 kB
Release files / assurance_cli-0.6.1.tar.gz
| Download URL | assurance_cli-0.6.1.tar.gz |
|---|---|
| Size | 68.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7900a063573a078428023e1f23d5dfc33615137b495423b31fba868cc220b099
|
|
BLAKE2b-256 checksum How to use checksums |
893b534542a5b579ae0e7fe9663021f32dd59ba8d646fe479f1eb1e88b09d629
|
| 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 Sep 24, 2026.
Transparency logRelease files / assurance_cli-0.6.1-py3-none-any.whl
| Download URL | assurance_cli-0.6.1-py3-none-any.whl |
|---|---|
| Size | 47.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2544e08e8860da62ca3ffe670013cd8f5d3f90f82a4ed2338a617d269d5f1287
|
|
BLAKE2b-256 checksum How to use checksums |
43042025f1d61baffb0872bcf92225103f49598894ce08aa3f7f707d34035196
|
| 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 Sep 24, 2026.
Transparency log
