audit-deps

Audits project dependencies for vulnerabilities, license risks, staleness, and version-pinning gaps.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill audit-deps-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-deps
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/audit-deps
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill audit-deps-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping software with vulnerable, abandoned, or improperly licensed dependencies creates security and legal exposure. This Skill runs a structured dependency hygiene pass across any stack so issues are found before production, not after. ## Core Features & Use Cases - Vulnerability Scanning: Runs the stack-native audit tool (pip-audit, cargo audit, govulncheck, bundle-audit, npm audit) and triages findings by severity with fix versions. - License Review: Classifies dependency licenses as permissive, copyleft, or problematic against a baseline policy, flagging GPL/AGPL and unknown licenses for review. - Staleness and Pinning Checks: Detects abandoned packages, major-version lag, open version ranges, and missing or stale lock files. - Use Case: Before a release, run the audit on a repo containing both package.json and requirements.txt to get one prioritized report covering CVEs, license flags, and unpinned dependencies across both ecosystems. ## Quick Start Run a dependency audit on this repository and report vulnerabilities, license issues, and outdated packages.

Frequently Asked Questions about audit-deps

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

FAQPage Schema
How do I scan project dependencies for known vulnerabilities?▼

Run the audit tool native to your stack, such as npm audit for Node, pip-audit for Python, cargo audit for Rust, or govulncheck for Go. Triage results by severity and prioritize Critical and High findings with their fix versions.

How to check dependency licenses for GPL or copyleft risk?▼

Inspect the declared license of each direct dependency and classify it as permissive (MIT, Apache-2.0, BSD), copyleft (GPL, LGPL, AGPL, MPL), or problematic (Unknown, Proprietary). Copyleft and unknown licenses should be flagged for legal review before shipping.

Does dependency auditing work across multiple stacks in one repo?▼

Yes. Detect each package manifest present, such as package.json, requirements.txt, Cargo.toml, or go.mod, and run the appropriate audit tool for each ecosystem. Results are then combined into a single consolidated report.

How do I detect abandoned or outdated npm packages?▼

Check each package's last release date on its registry and flag anything with no release in over two years. Also review repository commit activity and whether the installed version lags a major version behind the current stable release.

Why are open version ranges like * or latest a problem?▼

Open ranges allow silent dependency drift that can introduce regressions or unreviewed code into production builds. Prefer exact pins or tight ranges for production dependencies and always commit a lock file such as package-lock.json or Cargo.lock.