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

@polaroid-vhs/npm-health

v0.1.0

Published

CLI tool to analyze npm package health before you install it

Downloads

97

Readme

npm-health

🏥 Check the health of an npm package before you install it

A simple CLI tool that analyzes npm packages and gives you a quick health score based on:

  • How recently it was updated
  • Number of dependencies
  • License information
  • Repository availability

Why?

Before adding a new dependency to your project, you should know:

  • Is this package still maintained?
  • Does it have too many dependencies?
  • Is it licensed properly?

npm-health gives you this information in seconds.

Installation

npm install -g @polaroid-vhs/npm-health

Usage

npm-health <package-name>

Example:

$ npm-health chalk

📦 Health Check: chalk

Latest version: 5.6.2
Last published: 157 days ago
Dependencies: 10
License: MIT
Repository: https://github.com/chalk/chalk

Health Score: 100/100

✅ Package looks healthy!

Example with deprecated package:

$ npm-health request

📦 Health Check: request

Latest version: 2.88.2
Last published: 2193 days ago
Dependencies: 40
License: Apache-2.0
Repository: https://github.com/request/request

Health Score: 45/100

⚠️  Consider alternatives or check the package carefully before using.

Health Score

The health score (0-100) is calculated based on:

  • Last published (-40 if >2 years, -20 if >1 year)
  • Dependencies (-30 if >50, -15 if >20)
  • License (-10 if missing)

Scores:

  • 80-100: Healthy package ✅
  • 60-79: Use with caution
  • <60: Consider alternatives ⚠️

API

You can also use it programmatically:

import { checkPackage } from '@polaroid-vhs/npm-health';

const health = await checkPackage('chalk');
console.log(health);
// {
//   name: 'chalk',
//   version: '5.6.2',
//   daysSincePublish: 157,
//   dependencies: 10,
//   license: 'MIT',
//   repository: 'https://github.com/chalk/chalk',
//   description: 'Terminal string styling done right'
// }

Development

# Install dependencies
npm install

# Run tests
npm test

# Test CLI locally
node src/cli.js <package-name>

License

MIT © Polaroid