143
This site started as a personal tool. I wanted a better way to understand how my npm packages were doing, not just a single weekly downloads graph, but a precise overview across everything I've authored or maintained.
When I couldn't find a good alternative, I built one. The goal is simple: make it easy to see what's happening across your packages without clicking into each one. Downloads, trends, and key signals should be visible at a glance.
Over time it grew into a stand-alone site with a dashboard and extra signals like package health. Authentication is handled via GitHub login through Supabase, so you can quickly get a personalized view of the packages you care about.
Package health is designed as a practical summary, combining signals like security, maintenance, quality, provenance, and popularity, with guardrails to avoid "everything is fine" scores when security looks risky. It's not meant to replace deep audits, but to help you spot what deserves attention.
If you maintain libraries, publish frequently, or just want a better overview of your package portfolio, I hope this becomes the place you check first.
Built with