docs: add AUDIT.md — security & quality audit (status reflects current code)#141
docs: add AUDIT.md — security & quality audit (status reflects current code)#141john988 wants to merge 2 commits into
Conversation
…t status Multi-dimension audit of the pre-v1.4.0 local copy (73 confirmed findings). Most are already resolved by v1.4.0 and PR phuryn#140; the doc marks the three still genuinely open (scanner shrink-skip, today/week timezone, dashboard query cache) and records the refuted/safe items.
Scanner shrink-skip, today/week UTC dates, and dashboard /api/data caching are resolved; note the residual stale-turn limitation on compaction.
|
Thanks for putting this together, @john988 — a multi-dimension audit with per-finding verification is real work and genuinely useful. We treated it as a checklist rather than merging verbatim (matching your own framing). The confirmed findings are addressed — pricing/XSS/threading/test items in v1.4.0, the subagent rows in v1.5.0 — and the verified-safe items (the We're going to pass on keeping a static |
Summary
Adds AUDIT.md — a point-in-time security & quality audit of claude-usage. Docs-only; no code changes.
main, so the status column reflects the current code — it explicitly marks which findingsv1.4.0already resolved (pricing/XSS/threading/tests/…) and which are addressed elsewhere.PRAGMA table_info(...)/AGENT_TYPE_EXPRf-strings are not injectable (constants only),Path.home()+ dualsubagentsseparators are cross-platform-correct, and the CLI's derived cache rates equal the dashboard's explicit ones.Severity summary (confirmed)
0 critical · 2 high · 9 medium · 42 low · 20 info— the two "high" rows were the sameclaude-opus-4-8mispricing (already fixed in v1.4.0).Notes
ccusageintegration) for where certain items are addressed; that work is in a different PR and isn't part of this docs-only change.