Browse
MergeWarden logo

MergeWarden

Updated

In short

MergeWarden is a checkout-free AI PR-governance tool that gates AI-agent pull requests against declared repo scope, control-plane drift, and permissions.

What is MergeWarden?

MergeWarden is an AI PR-governance tool that gates AI-agent pull requests against a repository's declared boundaries for teams shipping code with coding agents. It runs as a checkout-free GitHub Action, a CLI (npx mergewarden scan), and a hosted web queue, and its analysis is deterministic: it never executes pull-request code and never calls a language model, so its findings are replayable from the base commit. MergeWarden's detailed risk scan checks four security boundaries: workflow permission escalation (write-access gains or dangerous triggers), agent-control-plane drift (edits to AGENTS.md, CLAUDE.md, and .mcp.json), untrusted prompt inputs that could reach agent prompts, and install-script additions in package manifests. It also enforces a machine-checkable scope contract, declaring the agent, task, and allowed_paths, so a reviewer can see when an agent's PR strays outside what it said it would change. For triage, it surfaces queue-ordering facts such as PRs with no linked issue, thin descriptions under 80 characters, an unused PR template, or oversized diffs above 50 files or 1,500 changed lines. MergeWarden is MIT-licensed and open source. It is aimed at maintainers and platform teams who merge a high volume of agent-authored PRs and need deterministic, auditable evidence rather than another AI reviewer.

What is MergeWarden used for?

Best for maintainers and platform teams who need to gate high volumes of AI-agent pull requests against declared scope and security boundaries before merge.

How much does MergeWarden cost?

Free

Free

Free / open source (MIT license)

View pricing

Pros and cons

Pros

  • Deterministic analysis that never runs PR code and never calls an LLM, so findings are replayable from the base commit
  • Detects agent-control-plane drift in AGENTS.md, CLAUDE.md, and .mcp.json, plus workflow permission escalation
  • Runs three ways: checkout-free GitHub Action, CLI (npx mergewarden scan), and a no-login hosted web queue
  • Machine-checkable scope contract (agent, task, allowed_paths) catches PRs that stray outside declared scope
  • MIT-licensed and open source

Cons

  • Narrowly scoped to policy/boundary gating; it is not a general AI code reviewer and does not judge code quality
  • The hosted web queue is described by the maker as a product experiment and caps at 30 PR summaries (10 for detailed review)
  • Requires teams to write and maintain scope contracts to get full value from the scope check
  • Aimed at GitHub workflows, so it fits teams already gating PRs in that ecosystem

Questions about MergeWarden

What does MergeWarden do?

MergeWarden is a GitHub Action and CLI that gates AI-agent pull requests against a repository's declared boundaries. It checks whether a PR stays within its declared scope, whether it edits agent-control-plane files (AGENTS.md, CLAUDE.md, .mcp.json), whether it escalates workflow permissions, and whether it adds install scripts, giving maintainers deterministic evidence before merge.

How much does MergeWarden cost?

MergeWarden is free and open source under the MIT license. There is no paid tier listed on its GitHub repository or landing page.

Does MergeWarden run the PR's code or use AI to review it?

No. MergeWarden is checkout-free and deterministic: it does not execute pull-request code and its analysis never calls a language model. It reads only the files required by its rules from the base commit, so results are replayable and auditable rather than probabilistic.

How do you run MergeWarden?

Three ways: as a GitHub Action added to .github/workflows, as a CLI with commands like 'npx --yes mergewarden scan https://github.com/owner/repo/pull/123' or 'npx --yes mergewarden triage owner/repo', or through the hosted web queue at sjh9714.github.io/mergewarden where you paste a repo name with no login.

What is agent-control-plane drift and why does MergeWarden check it?

Agent-control-plane files such as AGENTS.md, CLAUDE.md, and .mcp.json steer how future coding agents behave in a repository. An agent that edits its own instructions can quietly change what later agents are allowed to do, so MergeWarden flags changes to these files as a potential privilege-escalation path.

What are the best alternatives to MergeWarden?

Reviews

Sign in to rate and review MergeWarden.

Sign in to review

No reviews yet. Be the first to review MergeWarden!

Visit MergeWarden