Is rxjs healthy, maintained, and safe?
Maintained, but watch it — rxjs has real signals (drift, thin maintenance, or advisories) worth tracking.
The verdict
rxjs earns a health score of 55/100, a medium risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Maintained, but watch it — rxjs has real signals (drift, thin maintenance, or advisories) worth tracking.
Nothing has shipped since 22 February 2025 — over a year ago (522 days) — which points to a dormant project. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. 3 maintainers are listed on npm, so the project isn't hostage to any single contributor.
Security-wise, rxjs currently has a clean OSV record — no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
rxjs 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
- v7.8.2
- Last release
- 22 February 2025 (522 days ago)
- Total releases
- 169
- First release
- 4 March 2012
- Package age
- 14.4 years
- Maintainers
- 3
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is rxjs still maintained?
Partly — the most recent release was 22 February 2025 (522 days ago), so maintenance has slowed but not fully stopped.
Does rxjs have known security vulnerabilities?
No advisories are currently recorded for rxjs in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is rxjs safe to use?
Maintained, but watch it — rxjs 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
rxjs 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.