sd0xdev/sd0x-harness

dep-audit

Audit dependency security risks

First seen Apr 20, 2026

Installation

$ npx skills add sd0xdev/sd0x-harness --skill dep-audit

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from sd0xdev/sd0x-harness · top by installs.

npx skills add sd0xdev/sd0x-harness

Browse all from sd0xdev/sd0x-harness

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 188
License LICENSE
Default branch main
Open issues 3
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash(yarn audit:*), Bash(npm audit:*), Bash(pnpm audit:*), Bash(npx:*), Bash(bash:*), Read, Glob
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,758 B
  • docs SUMMARY.md 48 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 16 installs

SKILL.md

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

Step Goal Safety
audit Scan dependencies for vulnerabilities read-only

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):

Manifest Ecosystem Audit Command Fix Command
package.json + pnpm-lock.yaml Node (pnpm) pnpm audit --audit-level {LEVEL} pnpm audit --fix
package.json + yarn.lock Node (yarn) yarn audit --level {LEVEL} yarn audit --fix or npx yarn-audit-fix
package.json Node (npm) npm audit --audit-level={LEVEL} npm audit fix
pyproject.toml Python pip-audit or safety check pip-audit --fix
Cargo.toml Rust cargo audit cargo audit fix
go.mod Go govulncheck ./... (manual fix)
build.gradle Java ./gradlew dependencyCheckAnalyze (manual fix)

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