Faker
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
marakfotoverite
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used internally by Faker.js for template/format string interpolation on library-controlled data structures, not arbitrary user input. Legitimate use in this data-generation library. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in examples/js/jquery.js (bundled jQuery example), not library runtime code. jQuery's historical use of new Function() for JSON parsing is well-known and benign. | ai | |
| provenance | no-provenance | AI (provenance): Package is ~12 years old; no provenance attestation is expected for packages predating Sigstore. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 0 / 6 |
v0.7.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.