| FMRS | 57 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 11 / 20 | 18 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Developers and teams using AI coding assistants (e.g., Claude Code, Cursor).
- Projects with multiple context files and complex structure.
- Teams that need to maintain accurate agent context.
- Environments with strict security requirements for MCP configs (e.g., no hardcoded API keys).
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Projects that don't use AI context files.
- Simple, solo projects where files change infrequently (may be overkill).
- Non-critical projects that don't require strict context maintenance.
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - Reads context and config files in the project directory (e.g., CLAUDE.md, .mcp.json).
- Optionally reads user-level config files (e.g., ~/.claude/settings.json) and global MCP configs (with --mcp-global).
- Optionally reads agent history and memory files in the user's home directory (e.g., ~/.claude/history.jsonl) when session or skill audits are enabled.
- Optionally writes context files to fix broken paths when --fix is enabled.
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - Auto-fix (--fix) may modify files unexpectedly; preview with --fix-dry-run and review changes.
- Session audit accesses sensitive history files in the home directory; enable only in trusted environments.
- The tool reads config and context files that may contain secrets (e.g., API keys); ensure access is controlled.
- Redundancy checks may produce false positives as inferred content may vary by context.
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, GitHub Copilot | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 7 | 0 |
|---|