dependency-audit
Skill0 starsChanged 23 days agoMITView on GitHub
Audits npm/pip/cargo dependencies for known vulnerabilities, outdated packages, and license issues. Activate before releases or when CVE alerts are received.
- Installs packages
42 other projects use a version of this.
Adopted by
Most recently taken up by
- petr-korobeinikov/skillstheir own version, first seen Nov 8, 2026
- ymd38/dev-skillstheir own version, first seen Nov 8, 2026
- northraystudio/marudatheir own version, first seen Nov 8, 2026
- Smaui94/ClaudeSkillCollectiontheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- amkisko/prayerstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use api-audit, container-audit and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
gmanch94Skillapi-audit
Guides a structured API portfolio audit — from discovery through primary-source-verified inventory, shortcomings analysis, prioritized recommendations, executive summary, and options analysis. Enforces primary-source discipline, cross-file consistency, and advisor review gates. Use when auditing an API portfolio, evaluating a vendor's developer ecosystem, or producing defensible technical analysis of an API set.
Also in 3 projects that use this
grichaSkillcontainer-audit
Audit local Docker images and running containers for hardening issues before deploy — privileged flags, root users, stale base images, missing resource limits. Use for pre-deploy container review.
Also in 3 projects that use this
OpenAISkillthreat-model
Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Also in 4 projects that use this
renfei-designSkilla11y-audit
Audit Figma designs for WCAG accessibility issues — color contrast, minimum font size, touch target sizing, and missing text alternatives. Use when asked to check accessibility, audit contrast ratios, find a11y issues, verify WCAG compliance, or review designs for accessibility problems. Scans nodes, analyzes offline, and annotates issues in Figma.
Also in 3 projects that use this
GitHubSkillaccessibility-audit
Audits actual components and routes against applicable WCAG 2.2 A/AA criteria using consumer-owned design-system evidence and repository tools. Use when asked for an accessibility audit, a11y check, keyboard or focus review, contrast check, or screen-reader verification.
Also in 3 projects that use this
pproencaSkillrefactoring
Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles. This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.
Also in 3 projects that use this
Other versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 42
- web-infra-dev/modern.js★ 5ksame name
- briiirussell/cybersecurity-skills★ 489same name
- Mathews-Tom/armory★ 340same name
- PerryLink/dsh-skill-pack-security★ 22same name
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
- Quality-Max/free-qa-skills★ 13same name
- jnotsknab/mux-swarm★ 9same name
- greglas75/zuvo★ 7same name
- northraystudio/maruda★ 7same name
32 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- api-designSkill
- arch-constraint-guardSkill
- backend-patternsSkill
- clean-architectureSkill
- codebase-mappingSkill
- context-budgetSkill
- cqrsSkill
- ddd-architectureSkill
- debug-flowSkill
- django-patternsSkill
- django-tddSkill
- event-driven-architectureSkill
- fd-codenavSkill
- fd-mapSkill
- frontend-patternSkill
- git-releaseSkill
- git-workflowSkill
- golang-patternsSkill
- hexagonal-architectureSkill
- java-patternsSkill
- layered-architectureSkill
- performance-profilingSkill
- postgres-patternsSkill
- python-patternsSkill
- refactor-guideSkill
- research-firstSkill
- rust-patternsSkill
- saga-architectureSkill
- security-scanSkill
- tdd-workflowSkill
- test-gap-detectorSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Run security audit commands
- Distinctive: line 29
Check for outdated packages
- Distinctive: line 30
Check licenses of key dependencies
“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependency Audit Skill
Checks dependencies for security vulnerabilities, outdated versions, and license issues before they cause problems in production.
When to Activate
Activate when:
- Preparing a production release
- Receiving a CVE alert for a dependency
- Adding a major new dependency
- It has been more than 30 days since last audit
Core Principles
- Security over convenience — patch vulnerabilities before releasing
- Patch before releasing — critical and high findings block deployment
- License compliance matters — GPL in a commercial product can create legal problems
Workflow
- Run security audit commands
- Triage findings by severity
- Check for outdated packages
- Check licenses of key dependencies
- Produce report with recommended actions
Audit Commands
# npm
npm audit # all vulnerabilities
npm audit --audit-level=moderate # moderate and above
npm audit fix # auto-fix safe upgrades
npm audit fix --force # force fix (may break things — test first)
# Check outdated packages
npm outdated
# Snyk (more comprehensive)
npx snyk test
npx snyk monitor
# Python
pip-audit # install: pip install pip-audit
pip list --outdated
# Rust
cargo audit # install: cargo install cargo-audit
# Check licenses
npx license-checker --summary
npx license-checker --onlyAllow 'MIT;Apache-2.0;BSD-2-Clause;BSD-3-Clause;ISC'Severity Triage
| Severity | Action | Timeline |
| Critical | Fix immediately — do not deploy | Before next commit |
| High | Fix before release | Before next deployment |
| Moderate | Fix in next sprint | Within 2 weeks |
| Low | Track and fix eventually | Next maintenance window |
Common Vulnerability Patterns
- Prototype pollution — lodash <4.17.21, merge-deep <3.0.3
- Path traversal — file utility packages that accept user-controlled paths
- ReDoS — regex-based parsers (moment.js, validator.js older versions)
- Command injection — packages that shell out with user-controlled input
Update Strategy
| Change Type | Safety | Action |
| Patch (x.y.Z) | Very safe | Update immediately |
| Minor (x.Y.z) | Safe with tests | Update, run full test suite |
| Major (X.y.z) | Breaking changes likely | Read changelog, test thoroughly |
# Safe patch/minor updates
npm update # updates within version constraints
npx npm-check-updates -u --target patch # update only patchesLicense Audit
| License | Commercial Use | Notes |
| MIT | ✅ Safe | Most permissive |
| Apache 2.0 | ✅ Safe | Patent grant included |
| BSD-2/3 | ✅ Safe | Attribution required |
| ISC | ✅ Safe | MIT equivalent |
| LGPL | ⚠️ Check | OK if only linking to it |
| GPL | ❌ Risky | Legal review required for commercial |
| AGPL | ❌ Risky | Strongest copyleft — legal review required |
| Unknown | ❌ Investigate | Do not ship until license is known |
Output Format
## Dependency Audit Report
### Vulnerabilities
| Package | Severity | CVE | Fix |
|---------|----------|-----|-----|
| lodash@4.17.19 | High | CVE-2021-23337 | Upgrade to 4.17.21 |
### Outdated Packages (Major Versions)
| Package | Current | Latest | Breaking Changes |
|---------|---------|--------|-----------------|
| express | 4.17.3 | 5.0.0 | Yes — read changelog |
### License Issues
| Package | License | Issue |
|---------|---------|-------|
| some-pkg | GPL-3.0 | Requires legal review for commercial use |
### Verdict: PASS ✅ | FAIL ❌
FAIL if any Critical or High vulnerabilities remain unfixed.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

