dependency-analysis
Analyze project dependencies for security vulnerabilities, outdated packages, and upgrade paths. Use when auditing dependencies or planning upgrades.
When & Why to Use This Skill
This Claude skill automates the systematic analysis of project dependencies to identify security vulnerabilities, detect outdated packages, and map out clear upgrade paths. By supporting multiple ecosystems like Node.js, Python, and Go, it streamlines software supply chain security and ensures project maintainability through structured reporting and actionable insights.
Use Cases
- Security Auditing: Automatically scan project manifests for known CVEs and security risks in third-party libraries to prevent potential exploits.
- Maintenance Planning: Identify outdated packages and evaluate the complexity of version upgrades before starting development sprints.
- Pre-deployment Validation: Run a final dependency check as part of a CI/CD workflow or release checklist to ensure no high-risk vulnerabilities reach production.
- Legacy Code Assessment: Quickly generate a comprehensive health report for older codebases to prioritize technical debt and security patching.
| name | dependency-analysis |
|---|---|
| description | Analyze project dependencies for security vulnerabilities, outdated |
Dependency Analysis Skill
Purpose
Systematic analysis of project dependencies for security and maintenance.
When to Use
- Security audits
- Before adding new dependencies
- Planning version upgrades
- Regular maintenance checks
Analysis Process
Step 1: Identify Package Manager
Detect from files:
package-lock.json/yarn.lock/pnpm-lock.yaml→ Node.jsrequirements.txt/Pipfile.lock/poetry.lock→ Pythongo.sum→ Go
Step 2: Run Security Audit
Execute appropriate command:
# Node.js
npm audit --json || yarn audit --json
# Python (if pip-audit installed)
pip-audit --format json
# Go
govulncheck ./...
Step 3: Check Outdated
# Node.js
npm outdated --json
# Python
pip list --outdated --format json
# Go
go list -u -m all
Step 4: Analyze Results
Categorize findings:
- Critical: Security vulnerabilities with known exploits
- High: Security issues or major version behind
- Medium: Minor version behind or deprecated
- Low: Patch version behind
Output Format
Storage Location
Save to: docs/research/dependency-audit-{date}.md