@faker-js/faker
Generate massive amounts of fake contextual data
91%
Total Score
100
100
94
75
100
Health Score Breakdown
The project uses TypeScript, Vitest, and npm build tooling, but no security-scanning tools were detected. This is a modest transparency gap rather than evidence of unsafe maintenance.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All 10 workflows were analyzed and all 38 action references are pinned, with no untrusted checkout or script-injection paths. Low-confidence github-env and cache-poisoning findings plus two workflows with top-level write permissions are minor hygiene concerns, not standalone severe risks.
Vulnerabilities
| Title | Versions | Severity |
|---|---|---|
CVE-2026-73231 @faker-js/faker is vulnerable to Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in versions 0.0.0 - 10.4.0. | 0.0.0 - 10.4.0 | High |
Package versions
Maintainers
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 4 years ago
- Unpacked Size
- 2.8 MB
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.