# Dependency Audit Resolution

> Resolving npm audit or Dependabot high/critical alerts.

- Skill: `creanlab/dependency-audit-resolution` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add creanlab/dependency-audit-resolution`
- Raw SKILL.md: https://api.skillmd.com/api/skills/creanlab/dependency-audit-resolution/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: creanlab (https://skillmd.com/u/creanlab)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/creanlab/dependency-audit-resolution

---

# Dependency Audit Resolution

Resolving npm audit or Dependabot high/critical alerts.

## When to use
- When operating in the `security` domain.
- When resolving incidents related to dependency audit resolution.

## When not to use
- If the issue requires manual human intervention.
- If the domain does not apply.

## Triggers
- Pattern: `dependency-audit-resolution`
- Keywords: security, dependency

## Inputs
- Context from the current user session or incident report.

## Steps
### 1. Step 1
Review the vulnerability report to identify the vulnerable package and affected versions.

### 2. Step 2
Check if a patch is available and update the package using the package manager.

### 3. Step 3
If no patch is available, assess if the vulnerable code path is actually reachable in the current architecture.

### 4. Step 4
Run the test suite to ensure the update didn't introduce breaking changes.

## Success signals
- The task is resolved without regressions.
- Logs confirm the procedure was successfully applied.

## Failure modes
- Incorrect application of the steps leading to side effects.

## Safety notes
- Always verify changes in a staging environment before applying to production.
- Do not execute destructive commands without explicit authorization.