Security and privacy

Principles

Local first, least privilege, no telemetry, evidence over claims.

Controls and where they are tested

ThreatControlCheck
Hostile or huge HTML2 MiB, 30,000 element and depth-128 limits; linear-time parsingAS-A08, AS-F01, AS-F02
Symlink or non-regular inputlstat refusalAS-A09
Secrets or personal data in outputField values and placeholders never copied; observation notes limited and credential-like text rejectedAS-A04, AS-A10
XSS or link injection through file names or contentHTML escaping, strict CSP meta, Markdown escapingAS-A05
Tampered reports or ledgerSHA-256 seal; hash chainAS-A06, AS-A07
SSRF or scanning third partiesBrowser adapter allows only file: and loopback, blocks every other request, no credentials in URLAS-A12
Accidental form submissionAdapter only presses Tab; no clicks or typingcode review, docs
Local API abuseLoopback peers only, Host check, bearer token (24+ chars, constant-time compare), GET only, no CORS, rate limit, fixed file namesAS-A13, AS-A14
Overwriting user filesInstaller refuses the source repo, symlinks and existing destinations without --forceAS-A15
Misleading claimsSame disclaimer in every output; no scoresAS-A02, AS-A03, AS-A11
Supply chainZero runtime dependencies; npm provenance via trusted publishing; SHA-pinned release processCI

Residual risks

Reporting vulnerabilities

Use a private GitHub security advisory on the repository. Do not post exploits or tokens publicly.