dependency-audit · diff
git:20260922.be562dc to git:20260922.600ab82
5 added, 0 removed. Audit A to A.
---
name: dependency-audit
description: Run a weekly dependency audit for Composer or npm projects and propose a safe upgrade plan.
disable-model-invocation: true
+ context: fork
+ agent: leek-skills:dependency-auditor
+ background: false
allowed-tools: "Bash(composer outdated *) Bash(composer audit) Bash(composer audit *) Bash(npm outdated *) Bash(npm audit) Bash(npm audit *)"
---
# Dependency Audit Weekly
## Goal
Deliver a weekly dependency audit summary for the package manager this project uses.
+
+ In Claude Code with this plugin installed, this skill runs in its own `dependency-auditor` subagent (read-only, remembers packages the project has chosen to hold back); the report comes back to the main session when it finishes. In other harnesses it runs inline; the steps are the same.
## Detect package manager
Inspect the project root:
- `composer.json` present → **Composer** (PHP)
- `package.json` present → **npm** (JavaScript / TypeScript)
- Both present → audit **both**, report each section separately
- Neither present → stop and report that the directory is not a Composer or npm project
## Loop
Kickoff prompt (harnesses that support scheduled loops):
```text
/loop 7d Start the "Dependency Audit Weekly" loop.
Goal: deliver a weekly dependency audit summary.
Between iterations run the outdated command(s) for the detected manager(s).
Exit when: summary is posted with recommended upgrades.
```
### Composer
```bash
composer outdated --direct || true
composer audit || true
```
### npm
```bash
npm outdated || true
npm audit || true
```
Run security audit when a lockfile makes the result meaningful (`composer.lock`, `package-lock.json`, or `npm-shrinkwrap.json`).
## Report
Summarize the result with:
- Package manager evidence (`composer.json` / `composer.lock`, or `package.json` / lockfile, plus framework hints when relevant)
- Outdated **direct** dependencies grouped by patch, minor, and major updates
- Security advisories from the audit command, grouped by severity, when available
- Recommended safe upgrade order, starting with low-risk patch and minor updates
- Breaking-change risks, required code changes, runtime/framework constraints, or test coverage gaps for major updates
- Exact verification commands the project should run after upgrades
Keep the report direct. Do not apply upgrades unless the user asks you to do the upgrade work.
## Guardrails
- Do not modify the check command or exit criteria to force success.
- Do not skip, disable, or bypass checks to make the audit look clean.
- If package metadata is missing, dependency resolution fails, or audit output is blocked by registry/authentication issues, stop and report the blocker.