Skip to content
Back to skills

Dependency Audit

ASecurity

Runs a dependency audit workflow with supply-chain red flags and a required output template; use when adding or updating dependencies, handling security findings, preparing releases, or reviewing supply-chain risk in PRs.

  • 19 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
ai-agentsrustsecurity

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add sawrus/agent-guides --skill dependency-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dependency Audit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dependency Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sawrus-dependency-audit/badge)](https://www.skillsdirectory.com/skills/sawrus-dependency-audit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dependency-audit
description: "Runs a dependency audit workflow with supply-chain red flags and a required output template; use when adding or updating dependencies, handling security findings, preparing releases, or reviewing supply-chain risk in PRs."
---

# Skill: Dependency Audit

## When to load

When adding/updating dependencies, handling security findings, preparing releases, or reviewing supply-chain risk in PRs.

## Objective

Produce a dependency risk decision based on exploitability and business impact, not scanner output alone.

## Audit Workflow

1. **Inventory**
   - Identify direct and transitive dependencies changed in PR/release.
   - Record package source (registry), maintainer trust indicators, and version deltas.

2. **Scan**
   - Run ecosystem-native audit tools + repository policy checks.
   - Capture High/Critical findings with package path and affected components.

3. **Exploitability Triage**
   - Determine runtime reachability (is vulnerable code path invoked?).
   - Evaluate exposure (public endpoint, privileged process, internal-only).
   - Assess mitigations (WAF, sandbox, feature flags, auth boundaries).

4. **Classify each finding**
   - `exploitable-now` → block release, fix immediately.
   - `not-reachable` → document evidence and add VEX status.
   - `accepted-risk` → temporary exception with owner + expiry.

5. **Remediation Plan**
   - Prefer upgrade to patched version.
   - If upgrade is breaking: isolate vulnerability, add compensating controls, schedule upgrade milestone.

## Supply-Chain Red Flags

- Maintainer transfer shortly before suspicious release.
- Sudden dependency graph expansion unrelated to package purpose.
- install/postinstall scripts performing unexpected network activity.
- Obfuscated source in runtime package.
- Package source not in approved registries.

## Output Template (required)

- Dependency name and version delta
- Severity and advisory source
- Reachability evidence
- Classification (`exploitable-now` / `not-reachable` / `accepted-risk`)
- Decision and next action
- Owner and deadline

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.