Trustline
Business systems fail at the boundaries. Trustline verifies the boundaries.
Trustline compiles YAML contracts into SQL checks and produces a measurable integrity scorecard. See Why Trustline for the seam problem and compiler model.
Quickstart
pip install trustline
trustline audit --demo
The demo audit exits 1 — seeded failures are intentional. See ACME demo.
Scaffold contracts for your product:
trustline init --preset ml-crm-boundary --non-interactive
trustline validate --contracts ./trustline/contracts
Contributors: clone the repo and run make install-dev. See Getting Started.
When to use Trustline
Use Trustline when you need to verify seams between systems — not to orchestrate pipelines or train models:
| Scenario | Init preset |
|---|---|
| ML scores must land in CRM with expected coverage | ml-crm-boundary |
| Training and scoring read from different feature tables | cohort-source-parity |
| Identity funnel retention drops across join stages | funnel-retention |
| Block merges on invalid contract YAML in CI | trustline validate (no preset) |
List presets: trustline init --list-presets. Pattern details: Patterns. Walkthroughs: Use cases.
What Trustline is not
- Not an orchestrator — integrates with Airflow and Dagster; does not replace them
- Not a transform framework — extends dbt; does not replace it
- Not a model training runtime — no training, inference, or feature store
- Not a hosted SaaS — CLI you run in CI or on a schedule
- Not auto-remediation — detects and reports; never auto-fixes
Documentation
| Document | Description |
|---|---|
| Why Trustline | Problem statement and compiler model |
| Patterns | Boundary failure catalog |
| Use cases | Common adoption walkthroughs |
| Stability | Contract and CLI semver policy |
| Getting Started | Install, quick start, CLI |
| ACME demo | Bundled fixture and --demo |
| Overview | Commands, phases, architecture |
| Contract Spec | YAML schema |
| Roadmap | Planned versions |
| Examples | Init presets and templates |
| Contributing | Development |
Development
make check # format, lint, types, tests, coverage
make test
License
1 maintainer
Metadata
1 maintainer
Release files for trustline 0.2.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 | |
|---|---|---|---|
| trustline-0.2.0.tar.gz | 43.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trustline-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 108.3 kB
Release files / trustline-0.2.0.tar.gz
| Download URL | trustline-0.2.0.tar.gz |
|---|---|
| Size | 43.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d8ca81be9fa2317fe9835715c4449357d1c652f4e3c7684bc782804cea428d0
|
|
BLAKE2b-256 checksum How to use checksums |
eae40eadb8af2250c212a7599f915db8d2adca0fde5309c5cd738995bc7a9844
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 11, 2026.
Transparency logRelease files / trustline-0.2.0-py3-none-any.whl
| Download URL | trustline-0.2.0-py3-none-any.whl |
|---|---|
| Size | 64.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d50f23ef6d3a105011dfa6aa25a941a5964318ba3d4bb073f4e7d258d878ca28
|
|
BLAKE2b-256 checksum How to use checksums |
eef89f1cb91b8c0ecb601be31fdc23277d5c552831a9135a4af73d9d0ea23407
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 11, 2026.
Transparency log
