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

dep-graveyard

v1.0.0

Published

Scans your project dependencies (Node.js + Python) for abandoned, deprecated, and risky packages. Posts a report to Slack.

Readme

🪦 dep-graveyard

Scan your project dependencies for abandoned, deprecated, and risky packages — with a beautiful terminal report and Slack notifications.

Supports Node.js (package.json) and Python (requirements.txt) projects. Works on local folders or any GitHub URL — no cloning needed.

Usage (Zero Setup)

# Scan a GitHub repo instantly
npx dep-graveyard https://github.com/expressjs/express

# Scan your current project
npx dep-graveyard

# Fast mode (no AI summary)
npx dep-graveyard --no-llm

# Skip Slack notification
npx dep-graveyard --no-slack

What It Checks

| Risk | Signal | |------|--------| | 💀 CRITICAL | Package officially deprecated or yanked from npm/PyPI | | 🔴 HIGH | Package not updated in 2+ years | | 🟡 MEDIUM | Package not updated in 1+ year, or has a single maintainer | | ✅ SAFE | No issues found |

Environment Variables

Copy .env.example to .env and fill in your keys:

cp .env.example .env

| Variable | Required | Description | |----------|----------|-------------| | GROQ_API_KEY | Optional | Enables free AI plain-English summary of findings (get one at console.groq.com) | | SLACK_WEBHOOK_URL | Optional | Posts the full report to your Slack channel |

On macOS / Linux:

export GROQ_API_KEY="gsk-your-key-here"
export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..."
npx dep-graveyard

On Windows (PowerShell):

$env:GROQ_API_KEY="gsk-your-key-here"
$env:SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..."
npx dep-graveyard

Getting a Slack Webhook URL

  1. Go to api.slack.com/appsCreate an AppFrom scratch
  2. Click Incoming Webhooks in the sidebar → Toggle it ON
  3. Click Add New Webhook to Workspace and select a channel
  4. Copy the Webhook URL and add it to your .env file

Contributing (Local Development)

git clone https://github.com/YOUR_USERNAME/dep-graveyard.git
cd dep-graveyard
npm install
node src/cli.js https://github.com/expressjs/express --no-slack --no-llm

License

Apache-2.0