dep-check

Audit npm dependencies for vulnerabilities, outdated packages, and workspace mismatches.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill dep-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dep-check
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/dep-check
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill dep-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a quick, repeatable audit to find vulnerable or outdated npm packages and to detect version inconsistencies across monorepo workspaces so maintainers can fix dependency issues before they cause runtime bugs or release regressions.

Core Features & Use Cases

  • Security Audit: Runs a targeted production audit to surface recent vulnerabilities and their severity counts.
  • Outdated Major Versions: Identifies packages with available major upgrades that may require breaking-change reviews.
  • Workspace Consistency: Scans package.json files across the repo to report packages with conflicting version specifications and checks for duplicate shared package installations that can break React context or cause runtime duplication.
  • Use Case: Use this Skill as a pre-merge checklist in CI or as a local developer check after pnpm install to prevent dependency drift and security exposure.

Quick Start

Run a full dependency audit including security vulnerabilities, major-version outdated packages, and workspace version mismatches.

Frequently Asked Questions about dep-check

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

FAQPage Schema
How do I audit npm dependencies for vulnerabilities and outdated packages in a pnpm monorepo?

Auditing npm dependencies in a pnpm monorepo involves running pnpm audit and pnpm outdated commands to surface security vulnerabilities, severity counts, and packages requiring major version breaking-change reviews.

What's the best way to detect workspace version mismatches across package.json files?

Detecting workspace version mismatches requires scanning package.json files across the repository to report conflicting version specifications and duplicate shared package installations that cause React context or runtime duplication errors.

Does this dependency audit work with pnpm-managed workspaces in a CI workflow?

Yes, the dependency audit supports pnpm-managed workspaces and integrates into developer or CI workflows as a pre-merge checklist to prevent dependency drift and security exposure before pull requests.

Why do I need to check for duplicate shared package installations in a monorepo?

Checking for duplicate shared package installations is necessary because duplicates can break React context or cause runtime duplication errors. Scanning package.json files reports these shared package issues to prevent runtime bugs.

How can I prevent dependency drift and security exposure before a pull request?

Preventing dependency drift and security exposure before a pull request requires running a full dependency audit as a pre-merge checklist in CI or locally after pnpm install to identify vulnerable packages and workspace version inconsistencies.