Is fibers healthy, maintained, and safe?
Probably not. fibers has gone quiet for over two years and shows the hallmarks of an abandoned package.
The verdict
fibers earns a health score of 40/100, a medium risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Probably not. fibers has gone quiet for over two years and shows the hallmarks of an abandoned package.
The last sign of life was 30 August 2022, more than 4 years ago (1477 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. 4 maintainers are listed on npm, so the project isn't hostage to any single contributor.
Security-wise, fibers currently has a clean OSV record, with no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
fibers is usable but carries real signals, so 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
- v5.0.3
- Last release
- 30 August 2022 (1477 days ago)
- Total releases
- 59
- First release
- 23 January 2011
- Package age
- 15.7 years
- Maintainers
- 4
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is fibers still maintained?
It doesn't appear to be. The last release was 30 August 2022, over two years ago, which usually indicates an abandoned package.
Does fibers have known security vulnerabilities?
No advisories are currently recorded for fibers in the OSV database. That means none have been publicly disclosed and indexed, so it is not a guarantee of safety.
Is fibers safe to use?
Probably not. fibers has gone quiet for over two years and shows the hallmarks of an abandoned package. OSPulse rates it 40/100 (medium risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
fibers 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.