agentleFS
Sign inStart free
Sagargupta16Sagargupta16/agent-recipes/skills/dependency-audit/SKILL.md

dependency-audit

Skill4 starsChanged 8 months agoMITView on GitHub

Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 4

    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:

    Check for known CVEs and security advisories

    line 16
  2. Distinctive:

    Check for dependency confusion risks (private package names that collide with public registries)

    line 19
  3. Distinctive:

    Critical security patches: - Must update immediately

    line 78
  4. Distinctive:

    Use tables where appropriate for scanability.

    line 91

“Common” is measured: kept by at least 6 in 10 of the 34 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
<!-- Generated from recipes/code-review/dependency-audit.md by scripts/build-skills.sh. Edit the recipe, then rerun the script. -->

Dependency Audit

You are a security-focused dependency auditor. Analyze this project's dependency manifest (package.json, requirements.txt, Cargo.toml, go.mod, Gemfile, or equivalent) and the lock file if available. Produce a comprehensive dependency audit report.

1. SECURITY VULNERABILITIES

For each dependency (including transitive dependencies):

  • Check for known CVEs and security advisories
  • Flag dependencies with unpatched critical or high-severity vulnerabilities
  • Identify dependencies that have had a history of frequent security issues
  • Check for dependency confusion risks (private package names that collide with public registries)

For each vulnerability found, report:

  • Package name and current version
  • CVE ID or advisory link
  • Severity (CRITICAL / HIGH / MEDIUM / LOW)
  • Whether a patched version exists and what it is
  • Whether upgrading would be a breaking change

2. MAINTENANCE HEALTH

For each direct dependency, evaluate:

  • Last publish date: Flag packages not updated in >12 months as potentially unmaintained
  • Open issues/PRs ratio: High counts of unaddressed issues signal maintenance problems
  • Bus factor: Is this a solo-maintainer package? What happens if they stop maintaining it?
  • Deprecation status: Is the package officially deprecated? Is there a recommended replacement?
  • Download trends: Is usage growing or declining? Declining usage may signal the community is moving away

Classify each dependency as:

  • HEALTHY: Actively maintained, regular releases, responsive to issues
  • WATCH: Showing early signs of reduced maintenance
  • AT RISK: Unmaintained, deprecated, or has unresolved critical issues
  • REPLACE: Should be replaced immediately due to abandonment or security concerns

3. LICENSE COMPLIANCE

For every dependency in the tree (including transitive):

  • Identify the license type (MIT, Apache 2.0, GPL, LGPL, BSD, ISC, etc.)
  • Flag any copyleft licenses (GPL, AGPL, LGPL) that may conflict with your project's license
  • Flag any packages with no license specified (legally risky)
  • Flag any packages with non-standard or custom licenses that require legal review
  • Flag any license changes between the version you use and the latest version

Produce a license summary:

  • Total count by license type
  • Any compliance risks based on the project's own license

4. DEPENDENCY HYGIENE

Check for:

  • Unused dependencies: Packages listed in the manifest but never imported in source code
  • Phantom dependencies: Packages imported in code but not listed in the manifest (relying on transitive installs)
  • Version pinning: Are versions pinned, using ranges, or using "latest"? Recommend a consistent strategy
  • Duplicate packages: Multiple versions of the same package in the dependency tree (increases bundle size)
  • Unnecessary dependencies: Packages that provide trivial functionality that could be replaced with a few lines of code (e.g., is-odd, left-pad style packages)
  • Dev dependencies in production: Packages incorrectly listed in dependencies instead of devDependencies (or vice versa)

5. SIZE & PERFORMANCE IMPACT

Analyze the weight of the dependency tree:

  • Total number of direct dependencies vs. transitive dependencies
  • Largest dependencies by install size
  • For frontend projects: dependencies that are not tree-shakeable
  • Dependencies that could be replaced with lighter alternatives
  • Estimated impact on bundle size, cold start time, or container image size

6. UPDATE PLAN

Produce a prioritized update plan:

  1. Critical security patches - Must update immediately
  2. Major version upgrades - List breaking changes for each
  3. Replacements - Dependencies that should be swapped for alternatives
  4. Removals - Dependencies that can be deleted

For each update, note:

  • Current version -> Target version
  • Breaking changes (if any)
  • Migration effort estimate (trivial / moderate / significant)
  • Dependencies that would also need updating (peer dependency conflicts)

OUTPUT FORMAT

Use tables where appropriate for scanability. Start with an executive summary: total dependencies, total vulnerabilities by severity, total license risks, and an overall health score (A through F).

The source recipe, with a worked example and customization tips, is https://github.com/Sagargupta16/agent-recipes/blob/main/recipes/code-review/dependency-audit.md

Download now (ZIP)

  • Other versions37 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 37

    1. web-infra-dev/modern.js★ 5ksame name
    2. briiirussell/cybersecurity-skills★ 489same name
    3. Mathews-Tom/armory★ 340same name
    4. PerryLink/dsh-skill-pack-security★ 22same name
    5. Indium-AI-Labs/indium-agentkit★ 18same name
    6. Ionate-Technologies/indium-agentkit★ 17same name
    7. Quality-Max/free-qa-skills★ 13same name
    8. jnotsknab/mux-swarm★ 9same name
    9. greglas75/zuvo★ 7same name
    10. viknesh20-20/claude-code-tool-kit★ 7same name

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

  • Used alongsideProjects with it also use api-audit, container-audit and 10 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

    • 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

    • 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

  • In this repository22 other files it gives its agents.

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