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

deathwatch

v1.0.0

Published

Scan a project's dependencies and detect abandoned or dying packages

Readme

deathwatch

Scan a project's dependencies and detect abandoned or dying packages. Supports both npm (package.json) and pip (requirements.txt).

Install

npm install -g deathwatch

Usage

# Auto-detect package.json / requirements.txt in current directory
deathwatch

# Specify a directory
deathwatch --path ./my-app

# Custom thresholds (in months)
deathwatch --threshold 12 --warn 6

Options

| Option | Default | Description | |---|---|---| | --path <dir> | cwd | Directory to scan | | --threshold <months> | 12 | Months since last publish to flag as dead (red) | | --warn <months> | 6 | Months since last publish to flag as suspicious (yellow) |

Output

Each package is color-coded:

  • RED bold — dead (no update longer than --threshold months)
  • YELLOW — suspicious (no update longer than --warn months)
  • GREEN — healthy
  • GRAY — unknown (fetch failed or package not found)

Metadata shown per package:

  • Last updated (months ago)
  • Downloads/week (npm only; flagged if < 100/week)
  • [DEPRECATED] notice if the npm package is deprecated

A summary is printed at the end with total, healthy, suspicious, dead, and unknown counts.

What it checks

npm (via registry.npmjs.org)

  • Date of last publish
  • Whether the latest version has a deprecated notice
  • Weekly download count (flagged if < 100/week)

pip (via pypi.org/pypi/<pkg>/json)

  • Date of last release
  • Whether the package has any releases at all

Requirements

  • Node.js >= 18 (uses native fetch)

License

Apache 2.0