What happened to Faker.js and how to secure your projects

The golden rule when installing external javascript modules is that we should prefer popular packages that are frequently updated. The Faker.js library has met all this, and tens of thousands of developers have used it to generate random data such as people's names or company names as a useful tool, during development or tests.

Open Source Hacktivism, Git turns 17 & more

faker.js - Generate Massive Amounts of Fake Data

Log4Shell Vulnerability Highlights Software Supply Chain Issues, Data Center Knowledge

The right to delete: how faker.js exposed the fragile nature of open source culture, again

The npm faker package and the unexpected demise of open source libraries

How to create a Mock Server using Faker.js and JSON server, by shivaraj bakale

开源软件- The author of Faker.js deleted the library and ran away led to the shock in the open source circle: the open source project is now under the control of the

JFrog Helps Clean up Bad npm JavaScript with 3 New Tools - The New Stack

Developer sabotages open source modules colors.js and faker.js in NPM, affecting thousands of projects – Born's Tech and Windows World

How to generate auto demo data for .NET apps using Bogus

What Actually Happened to Faker.js: Open Source Contribution Lessons - DEV Community

Analyzing the Lifespan of Package Hijacking Attacks: What You Need to Know

What Really happened to Faker.js?, by Shashwat Agrawal

Developer Gets Suspended After Intentionally Damaging GitHub