Security and Privacy

Data handling

Everything stays on your machine. There are no network calls, no telemetry and no API keys. The tool reads only files you point it at, inside the workspace, and writes only .intentsutra/ and report folders you choose.

Threat model

ThreatControl in 0.2.1Test
Prompt injection in requirement or issue texttext is data; no LLM in the CLI; source labelled untrusted-inputrequirements tests
Path traversalinside() resolves against the real workspace root and rejects escapesrefuses path traversal
Symlink escapesymlinks refused for inputs, evidence, state dir, install target, report dirsymlink tests (skipped where the OS forbids creating links)
Oversized input2 MiB cap (5 MiB registry); import max 500 itemsrefuses oversized input
Secret leakageheuristic redaction of sk-, ghp_, password=-style strings in stored textunit test
Forged reviewernot preventable locally; labelled self-attested, identityVerified:false, audited (AUD-07)assurance tests
Evidence substitutionSHA-256 per link; re-checked at trace and audit (AUD-03)drift test
Audit rewritinghash chain; refuses to append when broken; AUD-01tamper test + 398 fuzzed byte edits
Silent registry editevery mutation must have an audit event (AUD-08)forgery test
Stale evidence promotionlink must match current revision; old links are historyrevision tests
HTML/Markdown injectionall output escaped; pipes escaped in tablesinjection tests + 200 fuzzed renders
Local API abuseloopback only, bearer token 24+ chars, GET only, no CORS, rate limitserver tests
Malicious test scriptsthe tool never executes tests or project codeby design
Cross-tenant accessnot applicable: single-user local tooln/a

Fuzzing

3000 randomized requirement records and 300 hostile import files produced no exception other than the intended IntentError. 398 single-character edits to the audit log were all detected. See test-results/fuzz-results.json.

Known limits (read these)

Reporting a vulnerability

Use GitHub private vulnerability reporting on the repository, or the contact in SECURITY.md. Do not post secrets in public issues.

Privacy

No personal data is collected by the tool. Reviewer names you type are stored in your own registry. Exported reports contain requirement text and file paths; review before sharing.