Kjell Tore Guttormsen 03b8885b6e chore(llm-security): v7.7.2 — language consistency pass

~/.claude/CLAUDE.md specifies English for code and documentation,
Norwegian for dialog only. Norwegian had crept into surface text
across v7.5-v7.7. Translated to English in eight surfaces.

No scanner, hook, or behavior changes — purely surface text.

- 18 skill commands: the HTML Report-step now reads "HTML report:
  [Open in browser]" instead of "HTML-rapport: [Åpne i nettleser]"
- scripts/lib/report-renderers.mjs: key-stat labels, lede defaults,
  table headers, maturity-ladder descriptions, action-tier labels,
  clean buckets, dry-run/apply copy, and JS comments. Regex
  alternations /^high|^høy/ and /resolution|løsning/i preserved.
- playground/llm-security-playground.html: same renderer changes
  mirrored bit-identical, plus playground-only UI strings (catalog,
  breadcrumb aria-label, theme toggle, builder-modal hint,
  guide-panel "no projects yet", delete confirmation, alert/copy).
  Demo-state fixture content for dft-komplett-demo preserved
  (intentional Norwegian persona).
- agents/skill-scanner-agent.md + agents/mcp-scanner-agent.md:
  Generaliseringsgrense + Parallell Read-strategi sections translated
  to Generalization boundary + Parallel Read strategy.
- README.md: playground architecture prose + Recent versions table
  (v7.5.0 — v7.7.1).
- CLAUDE.md: v7.7.1 highlights translated, new v7.7.2 highlights
  added.
- ../../README.md: llm-security v7.5.0 — v7.7.1 bullets.
- ../../CLAUDE.md: llm-security catalog entry.
- docs/scanner-reference.md: six runnable-examples table cells.
- docs/version-history.md: new v7.7.2 entry. v7.5-v7.7 narrative
  sections left in original language (deferred per operator).
- Version bumped 7.7.1 → 7.7.2 in package.json,
  .claude-plugin/plugin.json, README badge + Recent versions,
  CLAUDE.md header + state, docs/version-history.md, playground
  renderHome hardcoded string, root README + CLAUDE.md llm-security
  entries.

Tests: 1820/1820 green. CLI smoke-test: 18/18 commandIds produce
>138 KB self-contained HTML. Browser-dogfood verified.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-19 06:47:44 +02:00

2.4 KiB

Raw Blame History

name	description	allowed-tools	model
security:deep-scan	Run deterministic deep-scan — 9 Node.js scanners for Unicode attacks, entropy analysis, permission mapping, dependency auditing, taint tracing, git forensics, network mapping, memory poisoning, and toxic flow analysis	Read, Glob, Grep, Bash, Agent	sonnet

/security deep-scan [path]

9 deterministic Node.js scanners — entropy, Unicode, typosquatting, git forensics, taint tracing, dep audit, network mapping, memory poisoning, toxic flow analysis.

Step 1: Setup

$ARGUMENTS empty → target = cwd. Otherwise target = $ARGUMENTS (strip --deep).
Plugin root = parent of this commands/ folder.
Get temp path: node -p "require('path').join(require('os').tmpdir(), 'deep-scan-results.json')"

Step 2: Run Orchestrator

node <plugin-root>/scanners/scan-orchestrator.mjs "<target>" --output-file "<results_file>"

Exit 0=ALLOW, 1=WARNING, 2=BLOCK. Stdout = compact aggregate JSON. Full results in file.

Step 3: Show Banner

## Deep Scan: [VERDICT]
Risk Score: X/100 | Findings: XC XH XM XL XI
Scanners: X ok, X error, X skipped

Step 4: Synthesize Report

Spawn subagent_type: "llm-security:deep-scan-synthesizer-agent", model: "sonnet":

Read scan results from: <results_file> Read: <plugin-root>/knowledge/mitigation-matrix.md Produce complete report with actionable insights. Don't pad.

Output the synthesizer's report. If it fails, show banner + CRITICAL/HIGH findings from JSON.

Step 5: HTML Report

After producing the markdown deep-scan report (banner + synthesizer output or fallback):

Compute a temp markdown path:

node -p "require('path').join(require('os').tmpdir(), 'sec-deepscan-' + Date.now() + '.md')"

Use the Write tool to save the entire markdown report you just produced (banner + synthesizer narrative + scanner sections + findings) to that temp path. Verbatim.
Run the renderer:
```
node <plugin-root>/scripts/render-report.mjs deep-scan --in "<temp-md-path>"
```
The CLI writes reports/deep-scan-<YYYYMMDD-HHmmss>.html relative to CWD and prints file:///abs/path.html on stdout.
Append to your response (markdown link, no bare URL):

HTML report: Open in browser

If the CLI exits non-zero, mention the error but do not block — the markdown report above is the primary deliverable.

2.4 KiB Raw Blame History