@faker-js/fakerv9.2.0

Top 10k

Copy SHA256

License: Permissive (MIT)

Repository

npm

Homepage

Published:

Generate massive amounts of fake contextual data

Fail

Risk: Secrets

2 web service credentials found

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

2 web service credentials found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Downloads

409.06M

Recorded Downloads Since 2021

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

4.76K

Dependents

Issues per Version Graph

Scanned

FAQ for @faker-js/faker

What is @faker-js/faker?

Generate massive amounts of fake contextual data. For more information about this package, visit its homepage.

Is @faker-js/faker malicious or is it safe to use?

The npm package @faker-js/faker was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is @faker-js/faker popular?

The npm package @faker-js/faker ranks among the top 10000 projects in this community. It has 409M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure @faker-js/faker once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how @faker-js/faker behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a @faker-js/faker version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.