Is bluebird healthy, maintained, and safe?
Probably not. bluebird has gone quiet for over two years and shows the hallmarks of an abandoned package.
The verdict
bluebird earns a health score of 25/100, a high risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Probably not. bluebird has gone quiet for over two years and shows the hallmarks of an abandoned package.
The last sign of life was 28 November 2019, more than 6 years ago (2483 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. 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, bluebird currently has a clean OSV record, with no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
Treat bluebird 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
- v3.7.2
- Last release
- 28 November 2019 (2483 days ago)
- Total releases
- 228
- First release
- 24 September 2013
- Package age
- 13.0 years
- Maintainers
- 1
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is bluebird still maintained?
It doesn't appear to be. The last release was 28 November 2019, over two years ago, which usually indicates an abandoned package.
Does bluebird have known security vulnerabilities?
No advisories are currently recorded for bluebird in the OSV database. That means none have been publicly disclosed and indexed, so it is not a guarantee of safety.
Is bluebird safe to use?
Probably not. bluebird has gone quiet for over two years and shows the hallmarks of an abandoned package. OSPulse rates it 25/100 (high risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
bluebird 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-09-15 · scores are deterministic and recomputed on each refresh.