fs.extra
fs.move and fs.copy for Node.JS
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
coolaj86
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:fs-extra | AI (typosquat): fs.extra predates fs-extra and depends on it; not a typosquat, it's a wrapper package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process import is in test.js only, not in runtime code. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 3 / 1 |
v1.3.2
3 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'fs-extra'
typosquat
Package name 'fs.extra' is 1 edit(s) away from popular package 'fs-extra'.
Maintainer email 'awesome@[email protected]' uses domain '[email protected]' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
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.