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

proj-pulse

v1.0.1

Published

A health checkup for your project — dead deps, stale TODOs, unused env vars, and more.

Readme

🩺 proj-pulse

A health checkup for your project — one command to catch what's quietly rotting.

npx proj-pulse

What it checks

| Check | What it finds | |---|---| | 📦 Unused Dependencies | npm packages installed but never imported | | 🔐 Env Var Health | Missing keys, weak secrets, .env not in .gitignore | | 📝 Stale TODOs | TODO/FIXME comments older than 30 days | | 📁 Large Files | Source files over 500 KB that shouldn't be in git | | 🛡️ .gitignore Safety | Missing critical entries (node_modules, .env, etc.) |


Usage

npx proj-pulse "path/to/your/project"

Examples:

# Scan current folder
npx proj-pulse "./"

# Scan a specific project
npx proj-pulse "C:\Users\dev\my-app"
npx proj-pulse "/home/dev/my-app"

Example Output

  🩺 proj-pulse   Project Health Check

  Scanning: /Users/dev/my-app

  ✔  Unused Dependencies
     All 12 dependencies appear to be used.

  ⚠  Env Var Health
     2 env issues detected:
       · .env is NOT listed in .gitignore — risk of leaking secrets
       · Line 4: DB_PASSWORD — weak/short secret
     → Fix: Review your .env file and update insecure or missing values.

  ✖  Stale TODOs
     5 TODO/FIXME found, 3 older than 30 days:
       · [TODO] src/api/auth.js:42 — "refactor token handling" (87d old)
       · [FIXME] src/utils/parser.js:11 — "edge case for empty array" (63d old)
       · [HACK] src/db/index.js:7 — "replace with proper pool" (45d old)
     → Fix: Address or remove comments older than 30 days.

  ✔  Large Files
     No unexpectedly large source files found (threshold: 500 KB).

  ⚠  .gitignore Safety
     1 .gitignore issue found:
       · Missing: ".env"  (secrets / API keys)
     → Fix: Add missing entries to your .gitignore file.

──────────────────────────────────────────────────
  Summary

  ✔ Passed   2/5
  ⚠ Warnings 2/5
  ✖ Failed   1/5

  Health Score: 40%
──────────────────────────────────────────────────

Roadmap

  • [ ] --fix flag to auto-resolve safe issues
  • [ ] JSON output for CI integration (--json)
  • [ ] Config file (.proj-pulse.json) for custom thresholds
  • [ ] Git history analysis for churn / hotspot detection
  • [ ] Dead code detection

License

MIT