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.8 KiB

Raw Blame History

name	description	allowed-tools	model
security:dashboard	Cross-project security dashboard — machine-wide posture overview with per-project grades	Read, Glob, Grep, Bash	sonnet

/security dashboard

Machine-wide security dashboard. Discovers all Claude Code projects, runs posture-scanner on each, shows aggregated overview.

Step 1: Run Dashboard Aggregator

Run the aggregator (uses 24h cache by default):

node <this plugin's scanners/dashboard-aggregator.mjs>

If user specified --no-cache or --fresh, add --no-cache flag.

Parse the JSON output. The result contains:

meta.scanner, meta.version, meta.timestamp, meta.from_cache
machine.grade (weakest link), machine.projects_scanned, machine.total_findings, machine.counts
projects[] with path, display_name, grade, risk_score, risk_band, worst_category, worst_status, findings_count, counts
errors[] with path, display_name, error

Step 2: Format Dashboard

Present the results:

# Security Dashboard

| Field | Value |
|-------|-------|
| **Machine Grade** | [A-F] (weakest link) |
| **Projects Scanned** | [N] |
| **Total Findings** | [N] |
| **Scan Time** | [N]ms |
| **Cache** | [Fresh scan / Cached (age)] |

## Project Overview

| Project | Grade | Risk | Worst Category | Findings |
|---------|-------|------|----------------|----------|
[one row per project, sorted by grade (worst first)]

## Errors

[List any projects that failed to scan, if any]

Sort the project table by grade (F first, A last), then by risk score descending.

Step 3: Recommendations

If machine grade is A/B: "Machine posture is solid. Re-run after major changes or new plugin installs."
If machine grade is C: "Some projects need attention. Run /security posture in the worst-graded project."
If machine grade is D/F: "Significant exposure. Run /security audit in projects graded D/F."
If from_cache: "Results cached. Run /security dashboard --fresh for a live scan."

Step 4: HTML Report

After producing the markdown dashboard above:

Compute a temp markdown path:

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

Use the Write tool to save the entire markdown dashboard you just produced (header table with Machine Grade + Project Overview table + Errors + Recommendations) to that temp path. Verbatim.
Run the renderer:
```
node <plugin-root>/scripts/render-report.mjs dashboard --in "<temp-md-path>"
```
The CLI writes reports/dashboard-<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 dashboard above is the primary deliverable.

2.8 KiB Raw Blame History