dead-deps — what happened to your dependencies

Is faker still maintained?

No — faker stopped being maintained around January 2022. @faker-js/faker is a community fork that picked faker up and carried it on.

Status
No longer maintained
Last maintained
January 2022
Use instead
@faker-js/faker on npm
Succession
Maintained fork
Drop-in
yes — swap the import
Confidence
high

Is there a maintained fork of faker?

@faker-js/faker is a community fork that picked faker up and carried it on. @faker-js/faker is close enough to a drop-in replacement that most projects only change the dependency and the import.

How to migrate from faker to @faker-js/faker

Replace the dependency with @faker-js/faker and change require('faker') to const { faker } = require('@faker-js/faker'); the generator API is otherwise the same as faker 5.5.3.

Why faker is on this list

In January 2022 the original author removed the faker source from GitHub and published a 6.6.6 release that no longer worked, which broke builds across the ecosystem. Eight contributors formed the faker-js organisation, restored the code from the last good release and now publish it as @faker-js/faker. The unscoped faker package has received no releases since 6.6.6 on 5 January 2022.

The succession is settled: primary sources agree and the ecosystem has already moved.

faker alternatives

Beyond the primary recommendation, these are credible for faker's use case:

Check your own project for faker

npx dead-deps --all --min-state unmaintained

Run that in the directory holding your lockfile. If faker is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.

Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.

Evidence

Every claim on this page traces to a primary source. Check them:

See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.