Is classnames healthy, maintained, and safe?
Probably not — classnames has gone quiet for over two years and shows the hallmarks of an abandoned package.
The verdict
OSPulse scores classnames at 35/100 (high risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Probably not — classnames has gone quiet for over two years and shows the hallmarks of an abandoned package.
The last sign of life was 29 December 2023, more than 2 years ago (941 days); by any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. Two maintainers are listed; better than a lone author, but still a thin bench if one steps away.
On the security side, OSV has no advisories on record for classnames today. That's reassuring, but "no known advisory" is not the same as "no vulnerability" — it only means nothing has been disclosed and indexed yet.
Treat classnames as a liability to manage: review the evidence above, pin or patch, and evaluate alternatives. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Key facts
- Latest version
- v2.5.1
- Last release
- 29 December 2023 (941 days ago)
- Total releases
- 30
- First release
- 5 November 2014
- Package age
- 11.7 years
- Maintainers
- 2
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is classnames still maintained?
It doesn't appear to be — the last release was 29 December 2023, over two years ago, which usually indicates an abandoned package.
Does classnames have known security vulnerabilities?
No advisories are currently recorded for classnames in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is classnames safe to use?
Probably not — classnames has gone quiet for over two years and shows the hallmarks of an abandoned package. OSPulse rates it 35/100 (high risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
classnames is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.