Is chai healthy, maintained, and safe?
Maintained, but watch it — chai has real signals (drift, thin maintenance, or advisories) worth tracking.
The verdict
OSPulse scores chai at 55/100 (medium risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Maintained, but watch it — chai has real signals (drift, thin maintenance, or advisories) worth tracking.
The newest release dates to 22 December 2025, 218 days back — a gap long enough to suggest the pace is slowing. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. 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.
Security-wise, chai currently has a clean OSV record — no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
chai is usable but carries real signals — pin versions, watch for new advisories, and keep a fallback in mind. 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
- v6.2.2
- Last release
- 22 December 2025 (218 days ago)
- Total releases
- 110
- First release
- 7 December 2011
- Package age
- 14.7 years
- Maintainers
- 1
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is chai still maintained?
Partly — the most recent release was 22 December 2025 (218 days ago), so maintenance has slowed but not fully stopped.
Does chai have known security vulnerabilities?
No advisories are currently recorded for chai in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is chai safe to use?
Maintained, but watch it — chai has real signals (drift, thin maintenance, or advisories) worth tracking. OSPulse rates it 55/100 (medium risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
chai 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-28 · scores are deterministic and recomputed on each refresh.