/ Verzeichnis / Playground / repo-forensics
← Alle Server ↗ GitHub
● Community alexgreensh ⚡ Sofort

repo-forensics

von alexgreensh · alexgreensh/repo-forensics

18 defensive scanners that vet a repo, skill, MCP server, or plugin for prompt injection, secrets, lifecycle hooks, typosquats, and tamper traces before you install.

Repo-forensics is a defensive audit tool aimed at the 'nobody does it' problem: vetting third-party code before installing it with full system access. 18 parallel scanners cover runtime dynamism, manifest drift, prompt-injection in SKILL.md, MCP tool poisoning, DAST of hook scripts, secrets, SAST, AST analysis, dependency typosquats, lifecycle hooks, entropy payloads, IaC misconfigs, binary disguises, post-incident traces, and git-commit spoofing. Zero deps.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

repo-forensics-skill.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "repo-forensics-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json
{
  "context_servers": {
    "repo-forensics-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/alexgreensh/repo-forensics",
          "~/.claude/skills/repo-forensics"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add repo-forensics-skill -- git clone https://github.com/alexgreensh/repo-forensics ~/.claude/skills/repo-forensics

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: repo-forensics

Audit a third-party skill before you clone it into ~/.claude/skills

👤 Anyone installing skills from strangers on GitHub ⏱ ~15 min beginner

Wann einsetzen: Someone sent you a cool-looking skill link. Before clone, you want to know if it's safe.

Voraussetzungen
  • repo-forensics installed — git clone https://github.com/alexgreensh/repo-forensics ~/.claude/skills/repo-forensics
Ablauf
  1. Point at the target repo URL
    Use repo-forensics. Scan https://github.com/<author>/<skill> with the skill_threats, secrets, dataflow, and lifecycle scanners. Report findings.✓ Kopiert
    → Per-scanner report with severity flags
  2. Read correlated findings
    Any correlations across scanners — e.g. a secret-leak path plus a lifecycle hook?✓ Kopiert
    → Correlation summary

Ergebnis: A go / no-go decision grounded in scanner output, not vibes.

Fallstricke
  • Trusting a green scan as full proof of safety — Scanners are strong floor, not a ceiling — still read SKILL.md
Kombinieren mit: github · filesystem

Audit an MCP server for tool poisoning and rug-pull patterns

👤 Teams onboarding a new MCP into a production agent stack ⏱ ~20 min intermediate

Wann einsetzen: Before adding a new MCP server to an agent with real permissions.

Ablauf
  1. Run MCP-focused scanners
    Scan this MCP server repo with mcp_security, skill_threats, integrity, and dast.✓ Kopiert
    → Findings focused on tool descriptions and install scripts
  2. Check git history for identity spoofing
    Run git_forensics on the same repo — any spoofed commits?✓ Kopiert
    → Author / signing analysis

Ergebnis: An MCP security dossier before you wire it into your agent.

Run post-incident scanners after a suspicious install

👤 Anyone who just ran npm/pip install and feels uneasy ⏱ ~15 min intermediate

Wann einsetzen: Install finished with unexpected behavior; you want to know if something landed.

Ablauf
  1. Run post_incident + entropy scans
    Run post_incident scanner on ~/.npm and the current project. Also entropy scan the installed packages.✓ Kopiert
    → Flags for suspicious cached artifacts or encoded payloads

Ergebnis: Evidence of whether to rotate secrets and rebuild.

Fallstricke
  • Running scans from the potentially-compromised shell — Run from a fresh shell or another machine when in doubt

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

repo-forensics-skill + github

Pull a PR's diff and scan only the added files

Fetch PR #123 and run repo-forensics just on the files it adds.✓ Kopiert
repo-forensics-skill + filesystem

Scan a locally cloned repo and save a JSON report

Scan ./suspicious-repo and write findings.json next to it.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
skill_threats repo path Any skill audit 0
mcp_security repo path MCP audits 0
secrets repo path Always 0
dataflow repo path Suspicious egress concerns 0
lifecycle repo path Pre-install 0
git_forensics repo path Checking maintainer identity 0
entropy repo path Obfuscation suspected 0
sast repo path General code risk 0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
Moderate — scanner output summarization can grow
Kosten in €
Free
Tipp
Run only the scanners relevant to the threat model (skills → skill_threats; MCP → mcp_security)

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None — scanner is read-only
Datenabfluss: Local-only by default
Niemals gewähren: Write access to the repo under audit

Fehlerbehebung

Häufige Fehler und Lösungen

Scanner reports 0 findings on obviously sketchy repo

Ensure you ran against the full repo path, not a subset; check scanner selection

Prüfen: repo-forensics list-scanners
False positives flood the report

Filter by severity; focus on high/critical; use correlation to prioritize

Alternativen

repo-forensics vs. andere

AlternativeWann stattdessenKompromiss
claude-cybersecurityYour code needs OWASP-style app security review rather than supply-chain vettingDifferent focus — app logic vs install-time threats
gitleaks / trufflehogYou only need secret scanningSingle-scanner, not correlation

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen