Kjell Tore Guttormsen
03b8885b6e
~/.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>
94 lines
4.6 KiB
Markdown
94 lines
4.6 KiB
Markdown
---
|
|
name: security:plugin-audit
|
|
description: Audit a Claude Code plugin for security risks, permission analysis, and trust assessment before installation
|
|
allowed-tools: Read, Glob, Grep, Bash, Agent
|
|
model: sonnet
|
|
---
|
|
|
|
# /security plugin-audit [path|url]
|
|
|
|
Audit a Claude Code plugin for security before installation. Accepts local paths or GitHub URLs.
|
|
|
|
## Step 1: Resolve Target
|
|
|
|
- If `$ARGUMENTS` contains `--branch <name>` → strip it, set `branch = <name>`
|
|
- If `$ARGUMENTS` starts with `https://github.com/` or `git@github.com:` →
|
|
Run: `node <plugin-root>/scanners/lib/git-clone.mjs clone "<url>" [--branch <branch>]`
|
|
If exit code != 0 → show error to user and **STOP**
|
|
Set `clone_path` = stdout (trimmed), `target = clone_path`
|
|
Set `remote_url = <url>` for display
|
|
- Else if `$ARGUMENTS` is non-empty → `target = $ARGUMENTS`, `clone_path = null`
|
|
- Else → `target = "."`, `clone_path = null`
|
|
- Verify `.claude-plugin/plugin.json` exists at `<target>`. If not and `clone_path != null` → cleanup clone_path first, then tell user this is not a plugin directory and **STOP**. If not and local → tell user and **STOP**.
|
|
|
|
## IMPORTANT: Cleanup Guarantee (remote audits)
|
|
|
|
If `clone_path != null`, the following cleanup MUST run regardless of audit outcome.
|
|
If ANY step between clone and cleanup fails or errors, STILL run cleanup before stopping:
|
|
1. `node <plugin-root>/scanners/lib/git-clone.mjs cleanup "<clone_path>"`
|
|
2. `node <plugin-root>/scanners/lib/fs-utils.mjs cleanup "<evidence_file>"` (if `evidence_file` is set)
|
|
|
|
## Step 1.5: Pre-extraction (remote audits only)
|
|
|
|
If `clone_path != null`:
|
|
Get temp path: `node <plugin-root>/scanners/lib/fs-utils.mjs tmppath "plugin-extract.json"`
|
|
Run: `node <plugin-root>/scanners/content-extractor.mjs "<target>" --output-file "<evidence_file>"`
|
|
If exit code != 0 → set `evidence_file = null` (fall back to direct scan)
|
|
|
|
## Step 2: Inventory
|
|
|
|
Read plugin.json (name, version, auto_discover). Glob for commands, agents, hooks, skills, knowledge. Build permission matrix from all `allowed-tools` and `tools` declarations. Flag: Bash access, Bash+Write combo, Task (sub-agent spawning), opus for trivial tasks.
|
|
|
|
## Step 3: Analyze Hooks
|
|
|
|
If `hooks/hooks.json` exists: parse events, read scripts, classify (block/warn/modify). Flag: state modification, network calls, non-CLAUDE env vars, SessionStart hooks.
|
|
|
|
## Step 4: Scan Content
|
|
|
|
Spawn `subagent_type: "llm-security:skill-scanner-agent"`, `model: "sonnet"`:
|
|
|
|
If `evidence_file` is set:
|
|
> EVIDENCE-PACKAGE MODE. Read: \<evidence_file\>
|
|
> Read: \<plugin-root\>/knowledge/skill-threat-patterns.md
|
|
> Analyze all sections. DO NOT use Read/Glob/Grep on the target directory.
|
|
> Check all 7 threat categories. Return findings: file, severity, OWASP ref.
|
|
|
|
Otherwise:
|
|
> Scan plugin at \<path\>: commands/*.md, agents/*.md, hooks/scripts/*, skills/*/SKILL.md, knowledge/**/*.md.
|
|
> Read: \<plugin-root\>/knowledge/skill-threat-patterns.md
|
|
> Check all 7 threat categories. Return findings: file, severity, OWASP ref.
|
|
|
|
## Step 5: Report
|
|
|
|
Output: Plugin metadata, component inventory, permission matrix, hook analysis, security findings, trust verdict.
|
|
|
|
Verdict: **Install** (0 critical/high, transparent hooks) | **Review** (high findings or unclear permissions) | **Do Not Install** (critical, exfiltration, persistence, or hidden instructions).
|
|
|
|
## Step 6: Cleanup (only if remote)
|
|
|
|
If `clone_path != null`:
|
|
Run: `node <plugin-root>/scanners/lib/git-clone.mjs cleanup "<clone_path>"`
|
|
If cleanup fails → warn: "Could not remove temp dir <clone_path> — remove manually."
|
|
|
|
If `evidence_file != null`:
|
|
Run: `node <plugin-root>/scanners/lib/fs-utils.mjs cleanup "<evidence_file>"`
|
|
|
|
## Step 7: HTML Report
|
|
|
|
After producing the markdown plugin-audit report (Step 5) and any cleanup (Step 6):
|
|
|
|
1. Compute a temp markdown path:
|
|
```bash
|
|
node -p "require('path').join(require('os').tmpdir(), 'sec-plugin-audit-' + Date.now() + '.md')"
|
|
```
|
|
2. Use the Write tool to save the **entire markdown report you just produced** (plugin metadata + component inventory + permission matrix + hook analysis + security findings + trust verdict) to that temp path. Verbatim.
|
|
3. Run the renderer:
|
|
```bash
|
|
node <plugin-root>/scripts/render-report.mjs plugin-audit --in "<temp-md-path>"
|
|
```
|
|
The CLI writes `reports/plugin-audit-<YYYYMMDD-HHmmss>.html` relative to CWD and prints `file:///abs/path.html` on stdout.
|
|
4. Append to your response (markdown link, no bare URL):
|
|
|
|
> **HTML report:** [Open in browser](file:///abs/path.html)
|
|
|
|
If the CLI exits non-zero, mention the error but do not block — the markdown report above is the primary deliverable.
|