← Docs

Granska runs real scanner CLIs and an LLM review pipeline against attacker-controlled content — the whole point of an audit tool is to point it at code you don’t fully trust. That makes Granska’s own execution environment attack surface too, not just the thing producing a report about someone else’s. This page summarizes the honest, disclosed threat model; the full document (with the CodeRabbit RCE precedent this hardening was built in response to) is linked below.

What’s defended

What’s explicitly NOT defended

Why this matters

In 2025, a disclosed RCE in a comparable AI code-review product let a malicious pull request execute arbitrary code inside that product’s own production environment via a crafted linter config — reaching credentials across its install base. “The auditor is attack surface” is not hypothetical; Granska’s Phase 4 hardening exists because of exactly this threat class.

Full document, including every residual named explicitly: docs/THREAT-MODEL.md in the repo.