Is Your npm Package Still Maintained?
Enter any npm package to get a real-time health score — based on publish recency, download trends, GitHub activity, issue resolution and dependency risk.
Publish Recency
Days since last npm release
Download Trend
Growing, stable or declining?
GitHub Activity
Last commit, contributors
Issues Health
Open vs closed issue ratio
Maintainers
Bus factor and team size
Dependencies
Supply chain risk score
Popular Package Health Checks
react
UI Library
express
Web Framework
lodash
Utility
axios
HTTP Client
moment
Date Library
webpack
Build Tool
jest
Testing
typescript
Language
next
Framework
vite
Build Tool
eslint
Linter
prettier
Formatter
prisma
ORM
zod
Validation
tailwindcss
CSS
redux
State
zustand
State
framer-motion
Animation
@tanstack/react-query
Data Fetching
drizzle-orm
ORM
How the Health Score Works
Each package is scored across six dimensions with a maximum of 100 points. Publish recency (25pts) rewards packages with recent releases. Download trend (20pts) measures whether adoption is growing or shrinking. GitHub activity (20pts) checks when the last commit was made and whether the repository has been archived. Issues health (15pts) looks at the ratio of open to closed issues. Maintainer count (10pts) flags single-maintainer bus factor risk. Dependencies (10pts) scores packages with fewer transitive dependencies higher.
Grades run from A (85+) through F (below 30). A deprecated or archived package will score very low regardless of its download numbers — a package can still be widely downloaded while being unmaintained.