Dependency Audit

Trigger

• Keywords: dep audit, dependency audit, security audit dependencies, dep-audit

When NOT to Use

• OWASP code review (use /codex-security)
• Code review (use /codex-review-fast)
• General security review (use /codex-security)

Workflow Steps

Failure behavior: report-all

Task

Arguments

$ARGUMENTS

• --level <severity> — Minimum reporting level (low/moderate/high/critical), default: moderate
• --fix — Attempt automatic fix

Step 1: Check for audit script

Use Glob to check if .claude/scripts/dep-audit.sh exists in the project root.

• Found → run: bash .claude/scripts/dep-audit.sh $ARGUMENTS
  • If script succeeds, use its output and skip to the Output section.
  • If script fails, treat as a real audit failure (do not silently fallback).
• NOT found → skip to Step 2 (do NOT attempt to run the script).

Step 2: Fallback (no audit script)

Detect the project ecosystem and run the audit manually.

Ecosystem detection (check project root for manifest files):

Default {LEVEL} is moderate unless --level argument is provided.

If --fix is specified, run the fix command for the detected ecosystem after audit. If no recognized manifest file exists, report an error.

Output

## Audit Results

| Severity | Count |
|----------|-------|
| Critical | 0 |
| High | 0 |
| Moderate | 0 |
| Low | 0 |

## Vulnerability Details

### [severity] Issue Title

- **Package**: package-name
- **Fix**: Available / Not available

## Gate

✅ **PASS** — No moderate or above vulnerabilities
❌ **FAIL** — Found high severity vulnerabilities

Examples

/dep-audit
/dep-audit --level high
/dep-audit --fix