Skip to content
Skills Library
Security · Review & audit

dependency-audit

/dependency-audit

Analyzes project dependencies for known security vulnerabilities using npm audit, pip-audit, or similar tools. Use when auditing packages, checking for CVEs, or updating vulnerable dependencies.

Licence
MIT
Last repository change
27.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Analyzes project dependencies for known security vulnerabilities using npm audit, pip-audit, or similar tools. Use when auditing packages, checking for CVEs, or updating vulnerable dependencies.

Original author description

Analyzes project dependencies for known security vulnerabilities using npm audit, pip-audit, or similar tools. Use when auditing packages, checking for CVEs, or updating vulnerable dependencies.

How it works

  1. Quick Start
  2. Instructions
  3. Common Scenarios
  4. Report Format
  5. CI/CD Integration
Original SKILL.md headings · 193 lines, 463 words
SKILL.md preview
---
name: dependency-audit
description: Analyzes project dependencies for known security vulnerabilities using npm audit, pip-audit, or similar tools. Use when auditing packages, checking for CVEs, or updating vulnerable dependencies.
---

# Dependency Audit

## Quick Start

Audit dependencies based on project type:

```bash
# Node.js
npm audit

# Python
pip-audit

# Go
govulncheck ./...
```

## Instructions

### Step 1: Identify Package Manager

Check for manifest files:
- `package.json` / `package-lock.json` → npm/yarn
- `requirements.txt` / `pyproject.toml` → pip
- `go.mod` → Go modules
- `Cargo.toml` → Cargo (Rust)
- `Gemfile` → Bundler (Ruby)

### Step 2: Run Audit

**Node.js (npm):**
```bash
npm audit
npm audit --json  # Machine-readable output
```

**Node.js (yarn):**
```bash
yarn audit
yarn audit --json
```

**Python:**
```bash
pip install pip-audit
pip-audit
pip-audit -r requirements.txt
```

**Go:**
```bash
govulncheck ./...
```

**Ruby:**
```bash
bundle audit check --update
```

### Step 3: Analyze Results

Categorize by severity:

| Severity | CVSS | Action |
|----------|------|--------|
| Critical | 9.0+ | Update immediately |
| High | 7.0-8.9 | Update within 24h |
| Moderate | 4.0-6.9 | Update this sprint |
| Low | < 4.0 | Update when convenient |

### Step 4: Fix Vulnerabilities

**npm - Auto-fix:**
```bash
npm audit fix
npm audit fix --force  # Breaking changes allowed
```

**npm - Manual update:**
```bash
npm update vulnerable-package
# or specific version
npm install vulnerable-package@2.0.0
```

**Python - Update package:**
```bash
pip install --upgrade vulnerable-package
# or pin safe version in requirements.txt
vulnerable-package>=2.0.0
```

### Step 5: Verify Fixes

Re-run audit to confirm:
```bash
npm audit  # Should show 0 vulnerabilities
pip-audit  # Should show no issues
```

## Common Scenarios

### Transitive Dependencies

When vulnerability is in a sub-dependency:

```bash
# Check dependency tree
npm ls vulnerable-package

# Force resolution (npm)
# Add to package.json:
{
  "overrides": {
    "vulnerable-package": "2.0.0"
  }
}
```

### No Fix Available

When no patched version exists:
1. Check if vulnerability affects your usage
2. Consider alternative packages
3. Implement workarounds if possible
4. Monitor for updates

### Breaking Changes

When fix requires major version bump:
1. Review changelog for breaking changes
2. Update code to accommodate changes
3. Run tests thoroughly
4. Consider gradual rollout

## Report Format

```markdown
## Dependency Audit Report

**Project:** my-app
**Date:** 2024-01-15
**Total Dependencies:** 245
**Vulnerabilities Found:** 3

### Critical (1)

**lodash** - Prototype Pollution
- Installed: 4.17.15
- Fixed in: 4.17.21
- CVE: CVE-2021-23337
- Fix: `npm install lodash@4.17.21`

### High (1)

**axios** - SSRF Vulnerability
- Installed: 0.21.0
- Fixed in: 0.21.2
- CVE: CVE-2021-3749
- Fix: `npm install axios@0.21.2`

### Moderate (1)

**minimist** - Prototype Pollution
- Installed: 1.2.5
- Fixed in: 1.2.6
- CVE: CVE-2021-44906
- Fix: `npm audit fix`
```

## CI/CD Integration

### GitHub Actions

```yaml
- name: Audit dependencies
  run: |
    npm audit --audit-level=high
    # Fails if high or critical vulnerabilities found
```

### Pre-commit

```bash
# package.json scripts
{
  "scripts": {
    "precommit": "npm audit --audit-level=moderate"
  }
}
```

Versions

RepositoryScoreLicence
This page · armanzeroeight/fastagent-plugins100MIT
acaprino/alfio-claude-plugins100MIT
acaprino/alfio-claude-plugins100MIT
acaprino/alfio-claude-plugins100MIT
acaprino/alfio-claude-plugins100MIT
acaprino/alfio-claude-plugins100MIT
OKHP3/skillz100MIT
mathews-tom/armory100MIT
meyshad/skillforge100MIT

Database snapshot: 13.11.2026 · package version b92d1eb0ee46 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95memstack-security-dependency-audit
    Use this skill when the user says 'dependency audit', 'npm audit', 'pip audit', 'cargo audit', 'security vulnerabilities', 'outdated packages', 'supply chain', or needs to scan project dependencies for vulnerabilities, abandoned packages, and upgrade risks. Do NOT use for…
  • 84audit-dependencies
    Audit project dependencies for security vulnerabilities and outdated packages, then apply safe updates. Use when user says "audit my dependencies", "check for vulnerable packages", "run npm audit", "find security issues in my packages", "what packages are outdated", "update my…
  • 100iblai-vibe-security-dependency-audit
    Audit project dependencies, frameworks, languages, and dev tools for known vulnerabilities, CVEs, and security anti-patterns. Use when the user mentions 'dependency audit,' 'npm audit,' 'CVE,' 'vulnerable packages,' 'supply chain security,' 'outdated dependencies,' 'known…
  • 90ds-security
    Use when checking dependencies for vulnerabilities, patching vulnerable dependencies, or when a security review or codebase audit is requested.
  • 100deps-audit
    Use when auditing, updating, or securing project dependencies. Covers multi-language dependency detection, security vulnerability scanning, outdated package identification, unused dependency detection, and update strategies for npm, pip, cargo, and go.
  • 100snyk
    Snyk is a developer security scanner that finds known vulnerabilities in open-source dependencies, container images, infrastructure-as-code files and source code. Use when a user asks to scan for vulnerabilities, audit npm or pip packages, check a Docker image for CVEs, scan…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.