Causari MCP server

∵ causari

AI-written code has no author. It has causes. Causari proves them. How many lines from AI-tagged commits are still alive in your repo? One command, any git repo, no setup. A count, not a grade.

causari.dev  ·  Weekly Survival Report  ·  Method  ·  Manifesto  ·  Roadmap  ·  Releases

curl -fsSL https://causari.dev/install.sh | sh     # Linux / macOS (Windows below)

re audit                    # the repo you are in
re audit vercel/next.js     # any public repo, cloned to a temp dir and removed after

$ re audit
∵ causari · AI code survival
───────────────────────────────────────────────────
  36 commits analyzed (git metadata only, no setup required)

Verified AI-authored: 3 commits, 1773 introduced, 1773 survived (100.0%)
Probable AI-assisted: none detected
By agent (verified only)
  cursor                 1773 lines,   1773 survived (100.0%)

Confidence notes
  · VERIFIED = explicit metadata (trailers, bot author, etc.)
  · PROBABLE = weak heuristic; may include human-assisted commits
  · UNKNOWN commits are excluded from headline numbers
  · Only lines from AI-tagged commits are measured; inline completions
    (Copilot, Cursor Tab, …) leave no git trace and are invisible here
  · A measurement, not a grade: method at https://causari.dev/method

Everyone argues about how much code AI writes. Nobody can check the numbers. re audit reads plain git history — Co-Authored-By trailers, bot authors, agent markers — finds the commits that carry machine-readable AI authorship, and asks git blame how many of their lines are still at HEAD. No model, no estimate, no survey. Anyone re-runs it and gets the same bytes.

• --json the exact bytes behind any published row
• --summary Markdown for CI; --badge / --card one-colour SVGs
• --save append a snapshot to track your own trend

What it cannot see: code from inline completions (Copilot, Cursor Tab, Windsurf, …) leaves no git trace and counts as human. Commits without a trailer are UNKNOWN. A formatter pass or a moved function counts as a death under method v1. One bulk commit can dominate a line-weighted ratio; ratios under 5 AI-tagged commits are flagged. All of this is written out at causari.dev/method, with how to contest a number.

In CI: a count on every pull request

# .github/workflows/causari.yml
on: pull_request
permissions: { contents: read, pull-requests: write }
jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with: { fetch-depth: 0 }      # the audit reads every commit; shallow clones are wrong
      - uses: croviatrust/causari@v1

The Action downloads the prebuilt Linux binary (a few seconds), runs re audit --summary, writes it to the job summary and posts one sticky comment per PR. No cloud, no account. A live example.

The ledger: from "which commit" to "which prompt"

Shortened. The full README is on GitHub.