Steadfast Repository Governance

Official registry Developer tools

Local-first repository governance and verification tools for AI coding agents.

What can you do with Steadfast Repository Governance?

  • 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.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package steadfast-governance
Claude Code
claude mcp add steadfast-repository-governance -- uvx steadfast-governance==0.4.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "steadfast-repository-governance": {
            "command": "uvx",
            "args": [
                "steadfast-governance==0.4.1"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Steadfast
  2. Quick start
  3. The commands most people need
  4. What it checks—and what it cannot
  5. Configuration
  6. Project links
  7. Development

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

CommandPurpose
steadfast onboardSet up repository guidance and selected agent integration.
steadfast verifyRun the unified, read-only governance checks.
steadfast reportGenerate a human-readable audit report.
steadfast auditCheck changed files, evidence, contracts, and documentation drift.
steadfast discoverPrint a machine-readable capability map for tools and agents.
steadfast mcp-serverStart 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.

Development

python -m pip install -e .
python -m unittest discover -s tests -v
steadfast docs-check
steadfast code-truth

MIT licensed. See LICENSE.

Frequently asked questions

What is Steadfast Repository Governance?

Local-first repository governance and verification tools for AI coding agents.

How do I install Steadfast Repository Governance?

It runs on your machine. In Claude Code: claude mcp add steadfast-repository-governance -- uvx steadfast-governance==0.4.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Steadfast Repository Governance need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Steadfast Repository Governance open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Steadfast Repository Governance?

It is published by rllibo833-sudo. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.