Individual skill
audit-deps
Run a dependency vulnerability audit and map each advisory to the pracht routes, loaders, middleware, and API handlers that import the package. Use for "audit deps", "scan for CVEs", "npm audit", "which routes use this vulnerable package".
skills/audit-deps/SKILL.md
Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 106
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- cloudflare-workers Repository topic
- framework Repository topic
- full-stack Repository topic
- llms-txt Repository topic
- mcp Repository topic
- preact Repository topic
- ssg Repository topic
- ssr Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Pracht Audit Deps
`npm audit` (or `pnpm audit`) gives you a list of vulnerable packages. This
skill goes one step further: for each advisory, it tells you **which routes
and APIs touch the vulnerable code path** so you can prioritize and write
targeted regression tests after upgrading.
Prerequisites: `pracht inspect` requires a vite config that registers the
pracht plugin.
## Step 1: Run the audit
Detect the package manager from the lockfile in repo root; for yarn,
disambiguate Classic vs Berry via the `packageManager` field in