Is date-fns healthy, maintained, and safe?
Yes — date-fns looks healthy, actively maintained, and free of known advisories today.
The verdict
date-fns earns a health score of 85/100, a minimal risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Yes — date-fns looks healthy, actively maintained, and free of known advisories today.
Its most recent release shipped on 29 May 2026 — 59 days ago — so development is clearly active. Across 210 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
On the security side, OSV has no advisories on record for date-fns 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.
The signals are green today, but a clean snapshot is not a standing guarantee — packages drift. 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
- v4.4.0
- Last release
- 29 May 2026 (59 days ago)
- Total releases
- 210
- First release
- 6 October 2014
- Package age
- 11.8 years
- Maintainers
- 1
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is date-fns still maintained?
Yes — date-fns released as recently as 29 May 2026 (59 days ago), so it is actively maintained.
Does date-fns have known security vulnerabilities?
No advisories are currently recorded for date-fns in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is date-fns safe to use?
Yes — date-fns looks healthy, actively maintained, and free of known advisories today. OSPulse rates it 85/100 (minimal risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
date-fns 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.