agentleFS
Sign inStart free
viknesh20-20viknesh20-20/claude-code-tool-kit/.claude/skills/dependency-audit/SKILL.md

dependency-audit

Skill7 starsChanged 7 months agoMITView on GitHub

Audits project dependencies for known vulnerabilities, outdated packages, unused dependencies, and license compliance. Works with npm, pip, cargo, go modules, and more.

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

  • conorluddySkill

    performance-profiling

    Instruments integration and performance analysis workflows for iOS apps. Use when profiling CPU usage, memory allocation, network activity, or energy consumption. Covers Time Profiler, Allocations, Leaks, Network instruments, and performance optimization strategies.

    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

  • 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

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 5

    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 the appropriate audit command:

    line 25
  2. Distinctive:

    Run the appropriate command:

    line 47
  3. Distinctive:

    Look for dependencies that are imported in package manifest but never referenced in code:

    line 63
  4. Distinctive:

    Read the dependency list from the manifest

    line 65
  5. Distinctive:

    Check for problematic licenses:

    line 72

“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

Detect Package Manager

!ls package.json package-lock.json yarn.lock pnpm-lock.yaml bun.lockb 2>/dev/null !ls requirements.txt Pipfile Pipfile.lock pyproject.toml poetry.lock 2>/dev/null !ls go.mod go.sum 2>/dev/null !ls Cargo.toml Cargo.lock 2>/dev/null !ls Gemfile Gemfile.lock 2>/dev/null !ls *.csproj *.sln 2>/dev/null !ls composer.json composer.lock 2>/dev/null !ls mix.exs mix.lock 2>/dev/null

Audit Checks

1. Security Vulnerabilities

Run the appropriate audit command:

EcosystemCommand
npmnpm audit --json
yarnyarn audit --json
pnpmpnpm audit --json
pippip audit 2>/dev/null || pip-audit 2>/dev/null
Gogovulncheck ./... 2>/dev/null
Rustcargo audit 2>/dev/null
Rubybundle audit check 2>/dev/null
.NETdotnet list package --vulnerable 2>/dev/null
PHPcomposer audit 2>/dev/null

For each vulnerability found:

  • Package name and version
  • CVE ID or advisory ID
  • Severity (Critical/High/Medium/Low)
  • Fixed version (if available)
  • Whether it's a direct or transitive dependency

2. Outdated Dependencies

Run the appropriate command:

EcosystemCommand
npmnpm outdated --json
pippip list --outdated 2>/dev/null
Gogo list -m -u all 2>/dev/null
Rustcargo outdated 2>/dev/null
Rubybundle outdated 2>/dev/null

Classify updates:

  • Patch (1.0.0 → 1.0.1): Usually safe, bug fixes
  • Minor (1.0.0 → 1.1.0): New features, backward compatible
  • Major (1.0.0 → 2.0.0): Breaking changes, needs review

3. Unused Dependencies

Look for dependencies that are imported in package manifest but never referenced in code:

  1. Read the dependency list from the manifest
  2. For each dependency, search the codebase for imports/requires
  3. Flag any dependency with zero references as potentially unused

Note: Some dependencies are used via CLI, plugins, or config — verify before removing.

4. License Compliance

Check for problematic licenses:

  • Copyleft (GPL, AGPL): May require releasing your code
  • Permissive (MIT, Apache, BSD): Generally safe for commercial use
  • Unknown/No License: Risk — treat as all rights reserved

Output Format

Vulnerability Summary

PackageVersionSeverityCVEFix Available

Outdated Packages

PackageCurrentLatestUpdate TypeBreaking?

Potentially Unused

PackageLast Import FoundRecommendation

License Concerns

PackageLicenseRisk Level

Recommendations

  1. Immediate: Critical/High vulnerabilities with available fixes
  2. Short-term: Major version updates for key dependencies
  3. Backlog: Minor updates and cleanup of unused dependencies

Health Score

Rate dependency health from 0 to 10 (10 = all up to date, no vulns).

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.

Check your setup, free