Steadfast
Repository checks and guardrails for coding agents.
Steadfast is a local-first CLI that helps developers and AI agents inspect repository health, enforce change scope, verify evidence, and spot documentation drift. It does not generate code, require an AI API key, or send repository contents to a Steadfast-hosted service.
Quick start
Requires Python 3.10+ and Git.
python -m pip install --upgrade steadfast-governance
cd /path/to/your/repository
steadfast onboard --agent codex
steadfast verify
Replace codex with claude, cursor, or all to configure another supported agent. Review generated files before trusting a repository. Existing files are preserved by default.
For the latest unreleased source, install from Git instead:
python -m pip install --upgrade "git+https://github.com/rllibo833-sudo/Steadfast.git"
The commands most people need
| Command | Purpose |
|---|---|
steadfast onboard |
Set up repository guidance and selected agent integration. |
steadfast verify |
Run the unified, read-only governance checks. |
steadfast report |
Generate a human-readable audit report. |
steadfast audit |
Check changed files, evidence, contracts, and documentation drift. |
steadfast discover |
Print a machine-readable capability map for tools and agents. |
steadfast mcp-server |
Start the read-only MCP server for compatible agents. |
See the quick-start guide for a short walkthrough and the command reference for the full CLI list. For a copy-ready pull-request workflow and an adoption checklist, see Adopt in GitHub Actions.
What it checks—and what it cannot
- Scope: compare changed paths with repository policy.
- Evidence: check required proof files and evidence-bundle integrity.
- Security signals: flag selected risky source patterns and workflow trust-boundary issues.
- Documentation and code truth: detect stale command examples and package-entrypoint drift.
- Goals and releases: validate goal dependencies and evaluate release readiness.
- Agent support: discover skills, inspect MCP configuration, and install repo-local guidance.
These checks are guardrails, not a sandbox or proof of semantic correctness. Results depend on repository policy and configuration; review findings before treating them as release decisions. Steadfast does not silently rewrite plans or execute the configured pipeline as part of verify. Run steadfast pipeline separately only after reviewing its manifest.
Configuration
Run steadfast init to create starter governance files. Repository policy lives in .steadfast/policy.json; pipeline steps are configured in .steadfast/pipeline.json. Treat pipeline manifests as executable configuration and review their commands before running them.
Project links
- Source code and issues
- PyPI package
- Changelog
- Adoption and paid pilots
- Request an evaluation or collaboration
Development
python -m pip install -e .
python -m unittest discover -s tests -v
steadfast docs-check
steadfast code-truth
MIT licensed. See LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for steadfast-governance 0.4.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 | Provenance | |
|---|---|---|---|---|
| steadfast_governance-0.4.1.tar.gz | 112.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| steadfast_governance-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 219.7 kB
Release files / steadfast_governance-0.4.1.tar.gz
| Download URL | steadfast_governance-0.4.1.tar.gz |
|---|---|
| Size | 112.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a8d9306fdd22065acbf13ff7ba1b6e8bc74753f802ebb33fd51c4aacb2582a8
|
|
BLAKE2b-256 checksum How to use checksums |
578d2eaabf897ccbca22a9ec732b44b6a35654c0f8f446ac67f68d50fb38485f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 26, 2026.
Transparency logRelease files / steadfast_governance-0.4.1-py3-none-any.whl
| Download URL | steadfast_governance-0.4.1-py3-none-any.whl |
|---|---|
| Size | 106.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab8fd68c97d4d3d77fcf71cd32ff1db11a9464b5362f9a94807e82419545461c
|
|
BLAKE2b-256 checksum How to use checksums |
f5adb39ac8298feb4382ed0de35fd322f22bbc78b482b24cda12361a3d94b6dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 26, 2026.
Transparency logSecurity for steadfast-governance 0.4.1
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 steadfast_governance-0.4.1.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 26, 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.
