Is faker healthy, maintained, and safe?
No — faker looks abandoned and still has open security advisories.
The verdict
faker earns a health score of 10/100, a critical risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — faker looks abandoned and still has open security advisories.
The last sign of life was 5 January 2022, more than 4 years ago (1664 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.
OSV lists 1 known advisory for faker, including 1 high. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
The safest reading is to replace, fork, or tightly pin faker and stop taking on new exposure to it. 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
Known vulnerabilities (1)
Removal of functional code in faker.js
Key facts
- Latest version
- v6.6.6
- Last release
- 5 January 2022 (1664 days ago)
- Total releases
- 33
- First release
- 24 November 2013
- Package age
- 12.7 years
- Maintainers
- 1
- Known advisories
- 1
- Confidence
- High
Frequently asked
Is faker still maintained?
It doesn't appear to be — the last release was 5 January 2022, over two years ago, which usually indicates an abandoned package.
Does faker have known security vulnerabilities?
Yes — OSV lists 1 advisory for faker. See the advisory list on this page for the OSV/GHSA identifiers.
Is faker safe to use?
No — faker looks abandoned and still has open security advisories. OSPulse rates it 10/100 (critical risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
faker 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.