oh-my-triage 🩺
Connect your scanners. Let AI explain the noise.
Renamed from FindingBridge. The
findingbridgeCLI binary andfindingbridge_*MCP tools are gone, no deprecated aliases. On first run, oh-my-triage automatically migrates any legacyfindingbridge.config.json,~/.findingbridge/data, andFINDINGBRIDGE_*environment variables into the newoh-my-triage.config.json,~/.oh-my-triage/, andOMT_*names. After that one-time migration, the legacy names are not consulted again.
🤔 Why oh-my-triage?
As a developer, you've probably been overwhelmed by security scanner alerts. SonarCloud, GitHub Code Scanning, Semgrep, Trivy — each has its own interface, severity levels, and jargon. oh-my-triage connects these scanners and exposes their findings through MCP (Model Context Protocol) tools, so your AI assistant can help you understand, prioritize, and fix them.
Key principles:
- Scanner-agnostic: Not locked to any single scanner
- Privacy-first: Data stays local (SQLite by default)
- MCP-native: Works with Claude, Cursor, and any MCP client
- Open source: Self-hosted, no SaaS lock-in
✨ 3-Minute Quick Start
Method 1: Download & Run (Recommended for beginners)
- Download the release for your platform from Releases
- Extract and run
oh-my-triage(oroh-my-triage.cmdon Windows) - Follow the web setup wizard at
http://localhost:3456/setup - Ask Claude: "What are my most critical security findings?"
Method 2: npm (For developers)
npx oh-my-triage@latest server
# First run automatically opens the setup wizard
Method 3: Zero-Config Demo
npx oh-my-triage@latest server --demo
# Pre-loaded sample findings for instant exploration
🔌 Supported Scanners
🛠️ MCP Tools
All tools use the omt_ prefix:
🖥️ CLI Commands
oh-my-triage init # Initialize configuration
oh-my-triage setup # Run guided setup wizard
oh-my-triage setup --cli # CLI fallback (no browser)
oh-my-triage ingest --sarif <path> # Import SARIF file
oh-my-triage server # Start MCP server
oh-my-triage server --demo # Start with demo data
oh-my-triage config show # Show current config
oh-my-triage config test # Test scanner connections
oh-my-triage diagnose # Generate diagnostic report
🏗️ Architecture
┌─────────────────────────────────────────┐
│ LLM Agent (Claude / Cursor / Copilot) │
└─────────────────┬───────────────────────┘
│ MCP Protocol (stdio)
┌─────────────────▼───────────────────────┐
│ oh-my-triage MCP Server │
│ - 7 read-only tools │
│ - Structured JSON outputs │
└─────────────────┬───────────────────────┘
│
┌─────────────────▼───────────────────────┐
│ Core Engine │
│ - Normalization (severity mapping) │
│ - Deduplication (fingerprinting) │
│ - Prioritization (scoring) │
│ - Reporting (Markdown/HTML) │
└─────────────────┬───────────────────────┘
│
┌─────────────────▼───────────────────────┐
│ Adapters │
│ - SARIF File Reader │
│ - GitHub Code Scanning API │
│ - SonarCloud API │
│ - Socket.dev API │
│ - Snyk REST API │
│ - Semgrep API │
└─────────────────┬───────────────────────┘
│
┌─────────────────▼───────────────────────┐
│ SQLite (default) / PostgreSQL (opt) │
└─────────────────────────────────────────┘
🔒 Privacy & Security
- Data stays local: SQLite database in
~/.oh-my-triage/ - Token storage: System keychain (keytar) with env fallback
- No source upload: Only finding metadata + 20-line code snippets
- Secret redaction: Automatic redaction in logs and responses
- Read-only: No tools modify your repositories
📄 Documentation
🤝 Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
📄 License
Apache License 2.0 — see LICENSE for details.