A package.json accumulates cruft over time — duplicate entries, unpinned versions, missing metadata — that’s easy to miss in a quick glance but adds up to real maintenance risk. This tool surfaces those issues instantly.
What Is the package.json Analyzer?
The package.json Analyzer parses a pasted package.json file and reports dependency counts by section, lists all defined scripts, and flags common issues: unpinned (*/latest) versions, duplicate dependency declarations, missing standard fields, and known-deprecated packages.
How to Use It
- Open the tool at /tools/package-json-analyzer.
- Paste your package.json content.
- Review the overview stats, script list, and dependency counts.
- Check the “Potential issues” list for anything worth fixing.
Key Features
- Dependency, devDependency, and peerDependency counts at a glance.
- Unpinned version detection — flags
*andlatestversions that can silently change your build. - Duplicate-declaration detection across dependencies/devDependencies.
- Missing-field checks for name, version, license, test script, and repository metadata.
When to Use This Tool
- Auditing a package.json before a release or when onboarding to an unfamiliar project.
- Catching reproducibility risks from unpinned dependency versions.
- Quickly checking what scripts are available without opening an editor.
Try It Now
Open package.json Analyzer directly, or press ⌘K and type the tool name from anywhere on the site.
Part of the DevOps Tools collection on WebdevToolbox — free, browser-based developer tools with no login required.