agentleFS
troskatertroskater/flowdeck-claude/skills/dependency-audit/SKILL.md

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

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.
  • gmanch94Skill

    api-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

  • grichaSkill

    container-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

  • OpenAISkill

    threat-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-designSkill

    a11y-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

  • GitHubSkill

    accessibility-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

  • pproencaSkill

    refactoring

    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

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
  1. Distinctive:

    Run security audit commands

    line 27
  2. Distinctive:

    Check for outdated packages

    line 29
  3. Distinctive:

    Check licenses of key dependencies

    line 30

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Run security audit commands
  2. Triage findings by severity
  3. Check for outdated packages
  4. Check licenses of key dependencies
  5. 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

SeverityActionTimeline
CriticalFix immediately — do not deployBefore next commit
HighFix before releaseBefore next deployment
ModerateFix in next sprintWithin 2 weeks
LowTrack and fix eventuallyNext 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 TypeSafetyAction
Patch (x.y.Z)Very safeUpdate immediately
Minor (x.Y.z)Safe with testsUpdate, run full test suite
Major (X.y.z)Breaking changes likelyRead changelog, test thoroughly
# Safe patch/minor updates
npm update                         # updates within version constraints
npx npm-check-updates -u --target patch  # update only patches

License Audit

LicenseCommercial UseNotes
MIT✅ SafeMost permissive
Apache 2.0✅ SafePatent grant included
BSD-2/3✅ SafeAttribution required
ISC✅ SafeMIT equivalent
LGPL⚠️ CheckOK if only linking to it
GPL❌ RiskyLegal review required for commercial
AGPL❌ RiskyStrongest copyleft — legal review required
Unknown❌ InvestigateDo 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.