Skip to main content

assurance

Your AI agent says it's done. Assurance tells you what it didn't check.

uvx assurance audit          # in a project where you've used Claude Code
uvx assurance audit --demo   # or see a report on a bundled sample session

Real output on the bundled sample. The agent was asked to fix a rounding bug "and make sure the tests pass", and ended with "All done — the totals are correct now."

Claude Code session demo-8f2 — 13 min in /home/you/my-app
10 tool calls, 3 failed — Bash 6, Edit 2, Grep 1, Read 1

  Looped: 3 rounds of Bash `pytest -q tests/test_invoice.py` failing the same way, with nothing new read
  After the last edit (14:09): no test or check command ran
  Not classified: 2 shell commands (make lint-fix, python script), so whether they read, wrote or tested anything is unknown.
  Also in the transcript: 1 assistant turn, 1 user turn, 1 bookkeeping record.
  Not read: 0 lines.

Run it after every session. Add this to ~/.claude/settings.json. When Claude finishes without testing its last edit, you're told, and with --nudge Claude is sent back to run the tests:

{ "hooks": { "Stop": [ { "hooks": [ { "type": "command", "command": "uvx assurance audit --hook --nudge" } ] } ] } }

Every command

command question
assurance audit what did a Claude Code session actually do, and what did it skip?
assurance diff / assurance check did the work cover what it was supposed to, and what did it miss?
assurance pin did an MCP server change a tool definition after you approved it?
assurance deps what will a pip install or npm install execute, read without executing it?
assurance budget where did an agent run's budget go, and where did it loop going nowhere?
assurance authority may this task proceed for the person who asked?
assurance drift did a failure rate actually shift, or was the week noise?

Nothing here consults a model, opens the network, or reports a check it could not run as a pass.

This package contains no code of its own. It installs assurance-cli, assurance-deps, assurance-budget and assurance-authority, each of which also installs on its own. The MCP server is separate: pip install assurance-mcp.

Source, issues and documentation: https://github.com/i-ops-hq/assurance · Apache-2.0.

Release files for assurance 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for assurance 0.1.2
File Size Uploaded
assurance-0.1.2.tar.gz 7.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for assurance 0.1.2
File Interpreter ABI Platform
assurance-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 14.4 kB

Release files / assurance-0.1.2.tar.gz

Download URL assurance-0.1.2.tar.gz
Size 7.6 kB
Tags Source
SHA-256 checksum
How to use checksums
dc050116d548c83361c49af968c1e106cfce18ae69287b2162fc5f3d9d238d96
BLAKE2b-256 checksum
How to use checksums
d53f8c86ebec6af7490e1aee0dae2fed3f11bdc62873ca8c2a82582127e3540f
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

Release files / assurance-0.1.2-py3-none-any.whl

Download URL assurance-0.1.2-py3-none-any.whl
Size 6.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
110458b2e5c0fd5c0c85a3ce5f6598d5db96f0a112bb2c54bf3ff472cc380663
BLAKE2b-256 checksum
How to use checksums
fd7aaf92ee17afa64d384c9105e0cdd915de0e7c1c84b31455b8c4e059e4158c
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

Release history Release notifications | RSS feed

0.1.3

2 release files

This release

0.1.2 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page