dep-audit

Audits project dependencies for vulnerabilities, outdated versions, and safe upgrade paths.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/medispis/opencode-config --skill dep-audit-medispis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dep-audit
Source: https://github.com/medispis/opencode-config/tree/main/skills/dep-audit
Command: npx skills add https://github.com/medispis/opencode-config --skill dep-audit-medispis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects accumulate outdated and vulnerable dependencies over time, and manually checking each package across different ecosystems is slow and error-prone. This Skill runs the right audit commands for your package manager and turns raw output into a prioritized, actionable report. ## Core Features & Use Cases - Multi-ecosystem vulnerability scanning: Runs the correct audit tool for npm, pnpm, yarn, Python, Rust, Go, or Ruby based on detected lock files. - Risk classification: Sorts findings into Critical, High, Medium, and Low severity so you know what to fix immediately versus what can wait. - Upgrade planning: Distinguishes patch, minor, and major upgrades and flags breaking changes before recommending major version bumps. - Use Case: Before a release, ask for a dependency audit of your Node.js project and receive a report listing vulnerable packages like lodash with the exact fixed version, plus a table of outdated packages marked by upgrade type. ## Quick Start Audit the dependencies in this project and report any vulnerabilities and outdated packages with recommended upgrades.

Frequently Asked Questions about dep-audit

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

FAQPage Schema
How do I check my project for vulnerable dependencies?

Run the audit command matching your package manager, such as npm audit for Node.js, pip-audit for Python, or cargo audit for Rust. The Skill detects your lock file automatically, runs the right tool, and classifies each vulnerability by severity with a recommended fix.

How to find outdated npm packages and upgrade them safely?

Use npm outdated to list packages behind their latest versions, then apply patch updates immediately since they are safe. For minor upgrades check the changelog, and for major upgrades review breaking changes before updating, since code changes may be required.

What is the difference between npm audit and npm outdated?

npm audit reports known security vulnerabilities in installed packages, while npm outdated only shows packages behind their latest published version. A package can be outdated without being vulnerable, so both checks are needed for a complete dependency review.

Does dependency auditing work without a lock file?

Audits are less reliable without a lock file because the exact installed dependency tree cannot be determined. The Skill notes this limitation when no lock file exists, since vulnerability results may not reflect what is actually installed.

When should I not upgrade a dependency to the latest major version?

Avoid major upgrades when the changelog indicates breaking API changes that your code depends on, or when the package is loaded through dynamic imports that static analysis might miss. Plan these upgrades separately with testing rather than bundling them with patch updates.