dependency-audit

Audit project dependencies for vulnerabilities and supply-chain risks.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jtucker9/mystuff --skill dependency-audit-jtucker9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-audit
Source: https://github.com/jtucker9/mystuff/tree/main/skills/security/dependency-audit
Command: npx skills add https://github.com/jtucker9/mystuff --skill dependency-audit-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modern software relies on many dependencies, and insecure or abandoned packages create risk across the supply chain. This Skill identifies vulnerabilities and supply-chain risks in dependencies, enabling faster remediation and safer releases.

Core Features & Use Cases

  • Vulnerability scanning across multiple ecosystems (npm, pip, Cargo, Go, Ruby, PHP, etc.) to surface CVEs and risk indicators.
  • Supply-chain risk assessment, SBOM & license visibility, and a prioritized remediation plan.
  • Use Case: You inherit a legacy project with dozens of transitive dependencies; run this Skill to produce a risk report and a plan to upgrade or replace vulnerable components.

Quick Start

Run the audit against your project’s dependency files to generate a risk report and remediation plan.

Frequently Asked Questions about dependency-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Can I generate an SBOM and check license visibility for my software supply chain?

Yes, transitive dependency analysis is supported. This Skill traces vulnerabilities through nested dependency trees in your project files, identifying supply-chain risks in inherited packages to produce a comprehensive risk report.

Does this vulnerability audit work with both npm and Cargo ecosystems?

The best way to plan remediation for vulnerable dependencies is running this Skill to produce a prioritized risk report with actionable steps to upgrade or replace insecure components across supported ecosystems.

How do I identify supply-chain risks in abandoned or insecure packages?

Yes, this vulnerability audit works with npm, pip, Cargo, Go, Ruby, and PHP. It performs multi-ecosystem vulnerability detection and license visibility scanning to identify supply-chain risks across diverse project environments.

How do I identify supply-chain risks in abandoned or insecure packages?

You identify supply-chain risks in abandoned or insecure packages by running this audit against your project's dependency files, which surfaces known vulnerabilities and risk indicators to enable faster remediation and safer releases.