🗂 Dev Insight CLI

Dev Insight is a powerful and user-friendly CLI tool to analyze your Node.js project dependencies. It helps you quickly identify outdated packages, their semantic version impact, and export clean reports in Markdown, Excel, or JSON formats.

Features

• Detect outdated dependencies and devDependencies in your project
• Determine semantic version impact (major, minor, patch)
• Highlight zero-major-version (0.x) packages with special warning
• Export reports as:
  • Markdown (.md)
  • Excel (.xlsx)
  • JSON (.json)
• Interactive prompts for easy export selection
• Colorful terminal output with clear tables and summaries

Requirements

• Node.js (v20 or higher recommended)
• npm installed and accessible from your command line
• Internet connection to fetch package info from the npm registry
• A valid package.json file in your project directory

Installation

npm install -g dev-insight

or

npm i dev-insight

Usage

Run the CLI in your project directory:

dev-insight

or if you have installed using npm i dev-insight

npx dev-insight

Or specify a different directory:

dev-insight --dir /path/to/project

To output the results as JSON (for scripting or further processing):

dev-insight --json

📦 Example Output

• A table listing:
  • Package name
  • Declared version in package.json
  • Installed version
  • Latest available version on npm
  • Stable version (if available)
  • Indicator if it is a zero-major version (0.x)
  • Semantic version impact (Major, Minor, Patch)
• A summary box with counts of major, minor, and patch updates.
• Optional export report prompt after analysis:
  • No export
  • Markdown file (dev-insight-report.md)
  • Excel file (dev-insight-report.xlsx)
  • JSON file (dev-insight-report.json)

📝 License

MIT License © 2025 Created by Ashan MadhuWanta

Notes

• Packages marked with Yes under ZeroVer are using semantic versioning 0.x, which often means updates may contain breaking changes despite minor version bumps.
• The tool requires access to the npm registry to fetch latest package versions.
• Local or file-based packages (using file: or link: in package.json) are marked as local and skipped from version checks.