sentinel

/sentinel — Security Scan

Run a comprehensive security scan of the codebase. Available as CLI: magician-scan (plugin-provided; on PATH when the plugin is enabled).

For very large repos, raise /effort so the analysis stays thorough across the codebase. See lore/models.md.

Process

1. Static Analysis (via magician-scan)

SCAN=$(command -v magician-scan 2>/dev/null || echo "${CLAUDE_PLUGIN_ROOT}/bin/magician-scan")
[ -x "$SCAN" ] && "$SCAN" . || echo "magician-scan not found; skipping static-analysis step (continuing with remaining checks)"

magician-scan is plugin-provided (on PATH when the plugin is enabled). If absent, this step degrades gracefully and the remaining checks still run.

Reports: hardcoded credentials, private keys, eval() calls, SQL injection via % formatting, innerHTML XSS, dangerouslySetInnerHTML, os.system calls, shell=True subprocess.

2. Dependency Audit

Run for detected stack:

• Node.js: npm audit
• Python: pip-audit (if installed) or safety check
• Go: govulncheck ./... (if installed)
• Rust: cargo audit
• Java: OWASP dependency-check (if configured)

2.5 Dependency Supply-Chain Check

Known-CVE audits miss supply-chain attacks — the vector behind recent real incidents (litellm/PyPI, npm axios) where a plain install exfiltrates SSH keys, cloud creds, and env secrets. Check the install-time surface:

• Install-time scripts — flag lifecycle hooks that run arbitrary code on install:

  grep -rEn '"(preinstall|install|postinstall)"\s*:' package.json 2>/dev/null
  

  (Python equivalent: custom setup.py/pyproject.toml build hooks.)
• Recently added / unfamiliar deps — review new lockfile entries and dependencies that are typosquats of popular packages.
• Exfiltration shape — a dependency that reads credentials (~/.ssh, ~/.aws, env vars, wallets) and reaches the network is high-risk; escalate as Critical.
• Prefer lockfile integrity in CI (npm ci, not npm install) and pinned versions.

3. Secret Detection

Check for secrets in git history:

git log --all --full-history -p -- "*.env" "*.key" "*.pem" 2>/dev/null | grep -i "password\|secret\|key\|token" | head -20

4. Auth/Authz Spot Check

For web archetypes: identify all API endpoints and verify auth middleware is applied.

5. Input Validation Check

Scan for user input without sanitization.

Report Format

=== SENTINEL SECURITY REPORT ===
Date: <timestamp>
Target: <path>

CRITICAL: N
HIGH:     N
MEDIUM:   N
LOW:      N

[CRITICAL] src/auth.ts:45 — Hardcoded API key
[HIGH] src/db.ts:12 — SQL query built with string concatenation
...

DEPENDENCY AUDIT: N vulnerabilities found

OVERALL POSTURE: Clean | Needs attention | Requires immediate action

6. CI Integration Note

For CI pipeline use: magician-scan exits 0 (clean) or 1 (issues).

# .github/workflows/security.yml
- name: Security scan
  run: magician-scan .

Completion Signal

"Sentinel complete. . Review report above and run /scrutinize for systematic remediation."