dependency-auditor · alirezarezvani/claude-code-tresor — Claude Code skill for dependency audits
dependency-auditor is a skill that checks dependencies for vulnerabilities and license issues, then suggests fixes. Run it after dependency file changes or before deployment.
MIT ★ 788 updated 2026-07-03
npx skills add alirezarezvani/claude-code-tresor --skill dependency-auditor -a claude-codeWhat dependency-auditor does
The skill responds to changes in package.json, requirements.txt, lock files and other dependency files. It can also run when you ask about security or prepare a deployment. It identifies the package manager, starts an audit, groups findings by severity and recommends ways to address them. Checks cover known vulnerabilities, packages with security updates, malicious packages and license compatibility.
The listed package managers span Node.js, Python, Ruby, Java, Go and PHP. Audit commands include npm audit, pip-audit and bundle audit; sandboxed runs need access to package registries and suitable network permissions. Without registry access, an audit in the sandbox will fail. The skill can flag breaking-change risks and suggest manual or automatic updates.
What it helps with
- audit dependencies after changing
package.json - find vulnerable package versions before deployment
- sort audit findings by severity
- check dependency license compatibility
Example prompts for the agent
- Audit dependencies after I change
package.jsonand suggest fixes. - Check
requirements.txtfor vulnerable packages. - Before deployment, audit dependencies and flag high-severity findings.
How to install dependency-auditor
1Skills CLI (Vercel)
npx skills add alirezarezvani/claude-code-tresor --skill dependency-auditor -a claude-code2Manually: put the files in place
~/.claude/skills/dependency-auditor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dependency-auditor/
1Skills CLI (Vercel)
npx skills add alirezarezvani/claude-code-tresor --skill dependency-auditor -a codex2Manually: put the files in place
.agents/skills/dependency-auditor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add alirezarezvani/claude-code-tresor --skill dependency-auditor -a cursor2Manually: put the files in place
.cursor/skills/dependency-auditor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-code-tresor skills/security/dependency-auditor2Manually: put the files in place
.github/skills/dependency-auditor/SKILL.md1Skills CLI (Vercel)
npx skills add alirezarezvani/claude-code-tresor --skill dependency-auditor -a gemini-cli2Platform CLI
gemini skills install https://github.com/alirezarezvani/claude-code-tresor --path skills/security/dependency-auditorManually: put the files in place
.devin/skills/dependency-auditor/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about dependency-auditor
How do I install dependency-auditor in Claude Code?
Run npx skills add alirezarezvani/claude-code-tresor --skill dependency-auditor -a claude-code. The skill file is at ~/.claude/skills/dependency-auditor/SKILL.md.
What does dependency-auditor do?
It checks dependencies for known vulnerabilities and license issues, sorts findings by severity and suggests fixes.
Which package managers does dependency-auditor support?
The listed managers are npm, yarn and pnpm for Node.js; pip, pipenv and poetry for Python; Bundler, Maven, Gradle, Go modules and Composer. Sandboxed audits need package registry access.
Source text
SKILL.md · MIT
--- name: dependency-auditor description: Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency file changes, deployment prep, security mentions. allowed-tools: Bash, Read --- # Dependency Auditor Skill Automatic dependency vulnerability checking. ## When I Activate - ✅ package.json modified - ✅ requirements.txt changed - ✅ Gemfile or pom.xml modified - ✅ User mentions dependencies or vulnerabilities - ✅ Before deployments - ✅ yarn.lock or package-lock.json changes ## What I Check ### Dependency Vulnerabilities - Known CVEs in packages - Outdated dependencies with security fixes - Malicious packages - License compatibility issues - Deprecated packages ### Package Managers Supported - **Node.js**: npm, yarn, pnpm - **Python**: pip, pipenv, poetry - **Ruby**: bundler - **Java**: Maven, Gradle - **Go**: go modules - **PHP**: composer ## Example Alerts ### NPM Vulnerability ```bash # You run: npm install lodash # I automatically audit: 🚨 HIGH: Prototype Pollution in lodash 📍 Package: [email protected] 📦 Vulnerable versions: < 4.17.21 🔧 Fix: npm update lodash 📖 CVE-2020-8203 https://nvd.nist.gov/vuln/detail/CVE-2020-8203 Recommendation: Update to [email protected] or higher ``` ### Python Vulnerability ```bash # You modify requirements.txt: django==2.2.0 # I alert: 🚨 CRITICAL: Multiple vulnerabilities in Django 2.2.0 📍 Package: [email protected] 📦 Vulnerable versions: < 2.2.28 🔧 Fix: Update requirements.txt to Django==2.2.28 📖 CVEs: CVE-2021-33203, CVE-2021-33571 Affected: SQL injection, XSS vulnerabilities Recommendation: Update immediately to [email protected]+ ``` ### Multiple Vulnerabilities ```bash # After npm install: 🚨 Dependency audit found 8 vulnerabilities: - 3 CRITICAL - 2 HIGH - 2 MEDIUM - 1 LOW Critical issues: 1. [email protected] - SSRF vulnerability Fix: npm install axios@latest 2. [email protected] - Prototype pollution Fix: npm install ajv@^8.0.0 3. [email protected] - Information disclosure Fix: npm install node-fetch@^2.6.7 Run 'npm audit fix' to automatically fix 6/8 issues ``` ## Automatic Actions ### On Dependency Changes ```yaml 1. Detect package manager (npm, pip, etc.) 2. Run security audit command 3. Parse vulnerability results 4. Categorize by severity 5. Suggest fixes 6. Flag breaking changes ``` ### Audit Commands ```bash # Node.js npm audit npm audit --json # Structured output # Python pip-audit safety check # Ruby bundle audit # Java (Maven) mvn dependency-check:check ``` ## Severity Classification ### CRITICAL 🚨 - Remote code execution - SQL injection - Authentication bypass - Publicly exploitable ### HIGH ⚠️ - Cross-site scripting - Denial of service - Information disclosure - Wide attack surface ### MEDIUM 📋 - Limited impact vulnerabilities - Requires specific conditions - Difficult to exploit ### LOW 💡 - Minor security improvements - Best practice violations - Minimal risk ## Fix Strategies ### Automatic Updates ```bash # Safe automatic fixes npm audit fix # May include breaking changes npm audit fix --force ``` ### Manual Updates ```bash # Check what will change npm outdated # Update specific package npm update lodash # Major version update npm install lodash@latest ``` ### Alternative Packages ``` Vulnerable: [email protected] (deprecated) Alternative: axios or node-fetch Migration guide: [link] ``` ## Integration with CI/CD ### Block Deployments ```yaml # .github/workflows/security.yml - name: Dependency audit run: | npm audit --audit-level=high # Fails if HIGH or CRITICAL found ``` ### Scheduled Audits ```yaml # Weekly dependency check on: schedule: - cron: '0 0 * * 0' jobs: audit: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - run: npm audit ``` ## Sandboxing Compatibility **Works without sandboxing:** ✅ Yes **Works with sandboxing:** ⚙️ Needs npm/pip registry access **Sandbox config:** ```json { "network": { "allowedDomains": [ "registry.npmjs.org", "pypi.org", "rubygems.org", "repo.maven.apache.org" ] } } ``` ## License Checking I also check license compatibility: ``` ⚠️ License issue: GPL-3.0 package in commercial project 📦 Package: [email protected] 📖 GPL-3.0 requires source code disclosure 🔧 Consider: Find MIT/Apache-2.0 alternative ``` ## Best Practices 1. **Regular audits**: Run weekly or on every dependency change 2. **Update frequently**: Keep dependencies current 3. **Review breaking changes**: Test before major updates 4. **Pin versions**: Use exact versions in production 5. **Audit lock files**: Commit and audit lock files ## Related Tools - **security-auditor skill**: Code vulnerability detection - **@architect sub-agent**: Dependency strategy - **/review command**: Pre-deployment security check
© alirezarezvani · MIT · alirezarezvani/claude-code-tresor
Similar skills
All skills for Security →dependency-auditor by other authors comes first.