npm Package Dependency Analyzer

Modern JavaScript and TypeScript projects depend on dozens — sometimes hundreds — of npm packages. The package.json file records them under dependencies (needed at runtime) and devDependencies (needed only while developing, building, or testing). Keeping an eye on that list helps you spot outdated version patterns, oversized dependency sets, and categories that have grown unintentionally.

This tool parses your package.json and breaks the dependency list down in four ways: a summary count split between production and dev, a distribution of version-range styles (caret, tilde, exact, and so on), a grouping of packages into coarse categories such as Framework, Testing, and Build Tool, and an estimate of the total footprint. The result is a quick health check you can run before a release or during a dependency cleanup.

What it analyzes

• Counts — total, production, and dev-only dependency numbers.
• Version range distribution — how versions are pinned, from exact to floating ranges.
• Categories — a coarse grouping of each package by name pattern.
• Size estimate — a rough production-plus-dev footprint.
• Detailed table — every package with its version, type, and detected category.

What it does not do

• It reads only dependencies and devDependencies. peerDependencies, optionalDependencies, and transitive packages are not counted.
• Categories are inferred from package-name patterns, so an unusual name may land under "Other".
• The size figure is a heuristic estimate, not a measurement of your actual bundle.

1. Copy your package.json — Open your project's package.json file and copy the entire contents to your clipboard.
2. Paste into the input area — Paste the JSON content into the text area. You can also click "Example package.json" to see a sample analysis.
3. Click Analyze — The tool parses your dependencies and generates an analysis with statistics, charts, and a detailed table.
4. Review Insights — Check the summary cards for totals, the version range distribution for update patterns, and the dependency table for individual package details.

npm version specifiers control how much a dependency may drift when you run an install. The analyzer classifies each specifier into one of the following buckets.

Caret ranges are a common default because they receive compatible fixes without silently taking a breaking major release. A large cluster of exact pins can be a sign the project has not been updated in a while.

• Dependency cleanup — see how many packages a project carries before trimming unused ones.
• Reviewing a new dependency — check what type and category a package falls into and whether it is only needed at build time.
• Estimating footprint — get a rough sense of size impact before adding several packages at once.
• Auditing version styles — find projects that pin everything exactly or float everything with *.
• Documentation — summarise a project's dependency profile for a report or a README.