What is a package.json health checker?

A package.json health checker is a tool that analyzes your package.json file to identify issues, warnings, and suggestions. It evaluates factors like required fields, dependency versions, npm package quality scores, maintenance status, and best practices to give you a comprehensive health score for your project.

How does the health score work?

The health score is calculated on a scale of 0-100 based on various factors: missing required fields (name, version) reduce the score significantly, while missing optional metadata (description, license, repository) and dependency issues (loose versions, low-quality packages) also impact the score. A score of 90+ gets an 'A' grade, 80-89 is 'B', 70-79 is 'C', 60-69 is 'D', and below 60 is 'F'.

What npm data is analyzed for dependencies?

For each dependency, the tool fetches real-time data from the npms.io API including quality scores (code quality, testing, documentation), popularity metrics (download counts, GitHub stars), and maintenance status (update frequency, issue resolution). This helps identify outdated, poorly maintained, or low-quality packages in your project.

Is my package.json data secure?

Yes, all analysis happens entirely in your browser. Your package.json content is never sent to our servers. The only external requests made are to the public npms.io API to fetch package metadata, which only requires package names (not your full package.json). Your data remains completely private and secure.

What are the common issues found?

Common issues include missing required fields (name, version), invalid package names or version formats, missing license information, dependencies using loose version ranges (^, ~, *, latest), low-quality or poorly maintained packages, missing scripts, and lack of engine specifications. The tool provides specific recommendations for each issue found.

Can I download the analysis report?

Yes, after analyzing your package.json, you can click the 'Download Report' button to get a comprehensive text report containing your health score, all issues, warnings, suggestions, statistics, and detailed npm insights for each dependency. The report is saved as a .txt file with a timestamp.

How long does the analysis take?

The analysis itself is instant, but fetching npm data for dependencies takes longer depending on the number of packages. The tool processes packages in batches of 5 with delays to respect API rate limits. For a package.json with 20 dependencies, expect about 1-2 minutes. Progress is shown in real-time during the analysis.

What should I do with the suggestions?

The suggestions are recommendations to improve your package.json quality and maintainability. While not critical, implementing them can improve your project's discoverability, trustworthiness, and ease of maintenance. Prioritize adding a license, repository URL, description, and specifying exact dependency versions for production stability.

JSON Viewer

Package.json Health Checker

Full analysis with real-time npm insights for every dependency

Input package.json

Paste your package.json here...

Ready to Analyze

Paste or upload your package.json and click Analyze

Why Use Package.json Health Checker?

Comprehensive analysis tools to ensure your Node.js project dependencies are secure, up-to-date, and maintainable

Security & Quality Analysis

Get real-time npm package quality scores, security insights, and maintenance status for every dependency. Identify vulnerable or poorly maintained packages before they cause issues in production.

Comprehensive Health Scoring

Receive a detailed health score (0-100) with letter grades based on package.json completeness, dependency management, metadata quality, and npm package ratings. Track improvements over time.

Instant Dependency Insights

Analyze up to 30 dependencies instantly with detailed metrics including download counts, GitHub stars, license information, and popularity scores. Make informed decisions about your tech stack.

Privacy-First Analysis

All analysis happens entirely in your browser. Your package.json data never leaves your device. Only package names are queried from public npm APIs for metadata - your code stays private and secure.

Frequently Asked Questions

Everything you need to know about package.json health checking

Still have questions?

Can't find what you're looking for? Our support team is here to help you get the most out of our package.json health checker tool.

Contact Support