Open Collective
Open Collective
Change in maintainership
Published on January 21, 2022 by Jessica Sachs

👋 Hello Faker sponsors,

As you may be aware, there's been a change in maintainership and package location of the Faker package. 

Its new home on npm is:
npm install @faker-js/faker -D

Due to the recent events in early January where the original repository was deleted and maliciously updated, a fork has become available at @faker-js/faker and the community has converged on a new set of eight (!!) experienced maintainers from a variety of companies and Core teams within OSS.

A simple library does not *require* such a large number of maintainers, however the larger team gives the project additional protection from similar future incidents. Additionally, we have already begun improving the project and will be continuing to nurture the Faker package and its surrounding ecosystem.

In the last 14 days, this fork has become the primary home of Faker and we’ve merged in all other major forks.


For those who were sponsoring this project as a way to directly sponsor Marak, you can continue to sponsor him via the legacy fakerjs collective. Please read the team's statement for more details.

As for some wins: We’re hard at work improving the project’s health and hygiene.
* We’ve released 3 new alpha versions.
* We’ve already completed a full TypeScript migration so that the externally maintained @types/faker package will no longer be necessary as of Version 6.
* We’ve triaged and closed a ton of issues and PRs.

Check out the GitHub stats attached.

A huge shoutout to Shinigami for his impact, positivity, and drive.

Thanks to all of you for your continued support.

— Jess
@_JessicaSachs

Marak Squires

Posted on January 21, 2022

Duane O'Brien

Posted on January 21, 2022

First class update, thank you!
❤️  1

SpaceVim

Posted on April 30, 2022

 https://github.com/faker-js/faker is a illegal fork!