Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
johnlindquist avatar

Deps

  • 33 installs
  • 24 repo stars
  • Updated December 19, 2025
  • johnlindquist/claude

Audit and visualize dependencies in your project identifying security vulnerabilities and version conflicts.

About

Dependency scanner that lists installed packages and checks for known vulnerabilities. Works with npm, pip, Cargo, and more.

  • Multi-language dependency auditing
  • Security vulnerability detection with recommendations

Deps by the numbers

  • 33 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #3,349 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/johnlindquist/claude --skill deps

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs33
repo stars24
Last updatedDecember 19, 2025
Repositoryjohnlindquist/claude

What it does

Audit and visualize dependencies in your project identifying security vulnerabilities and version conflicts.

Files

SKILL.mdMarkdownGitHub ↗

Dependencies Manager

Audit, analyze, and manage project dependencies.

Prerequisites

At least one package manager:

# npm (comes with Node.js)
node --version

# yarn
npm install -g yarn

# pnpm
npm install -g pnpm

For dependency analysis:

npm install -g depcheck

CLI Reference

Security Audit

npm
# Run security audit
npm audit

# JSON output
npm audit --json

# Only production deps
npm audit --omit=dev

# Fix automatically
npm audit fix

# Fix with breaking changes (careful!)
npm audit fix --force
yarn
yarn audit
yarn audit --json
pnpm
pnpm audit
pnpm audit --json

Check Outdated Packages

npm
# List outdated
npm outdated

# JSON output
npm outdated --json

# Long format with details
npm outdated --long
yarn
yarn outdated
pnpm
pnpm outdated
pnpm outdated --json

Upgrade Packages

npm
# Update to latest within semver range
npm update

# Update specific package
npm update lodash

# Install latest (ignoring semver)
npm install lodash@latest

# Interactive upgrade (with npm-check)
npx npm-check -u
yarn
yarn upgrade
yarn upgrade lodash
yarn upgrade lodash@latest
yarn upgrade-interactive
pnpm
pnpm update
pnpm update lodash
pnpm update lodash --latest
pnpm update --interactive

Dependency Analysis

Why is this package installed?
# npm
npm explain lodash
npm ls lodash

# yarn
yarn why lodash

# pnpm
pnpm why lodash
Find unused dependencies
npx depcheck

# JSON output
npx depcheck --json

# Ignore patterns
npx depcheck --ignores="@types/*,eslint-*"

View Package Info

# View package details
npm view lodash

# Specific fields
npm view lodash version
npm view lodash versions
npm view lodash dependencies
npm view lodash repository.url

# JSON output
npm view lodash --json

Dependency Tree

# Full tree
npm ls

# Specific depth
npm ls --depth=2

# Production only
npm ls --omit=dev

# Specific package
npm ls lodash

# JSON
npm ls --json

Workflow Patterns

Security Audit Workflow

# 1. Run audit
npm audit --json > audit-report.json

# 2. Review high/critical
npm audit --audit-level=high

# 3. Auto-fix what's safe
npm audit fix

# 4. Manually review remaining
npm audit

Upgrade Workflow

# 1. Check what's outdated
npm outdated --json

# 2. Test current state
npm test

# 3. Update patch/minor versions (safer)
npm update

# 4. Test again
npm test

# 5. Update major versions one at a time
npm install package@latest
npm test

Dependency Cleanup

# 1. Find unused deps
npx depcheck

# 2. Review and remove
npm uninstall unused-package

# 3. Verify
npm test && npm run build

Investigating a Package

# Package info
npm view express

# Current version in project
npm ls express

# Who depends on it
npm explain express

# Security vulnerabilities
npm audit | grep express

Common Issues

Peer Dependency Warnings

# See peer deps
npm ls --json | grep peer

# Install missing peer deps
npm install missing-peer-dep

Version Conflicts

# See duplicate packages
npm ls --all | grep "deduped"

# Force dedupe
npm dedupe

Lock File Issues

# Regenerate lock file
rm package-lock.json
npm install

# Or for yarn
rm yarn.lock
yarn install

Best Practices

1. Audit regularly - Run npm audit weekly or in CI 2. Update incrementally - One major version at a time 3. Test after updates - Always run tests post-update 4. Review before fixing - npm audit fix --force can break things 5. Clean unused deps - Run depcheck periodically 6. Lock versions - Commit lock files to git 7. Check before adding - Review package health before installing

Related skills

Backend & APIsintegrationsbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.