fs-ext
1
Versions
—
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
msergeant
Keywords
fsfilesystemflockseek
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): Native C++ addon; node-gyp build is the standard and expected install pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:fs-extra | AI (typosquat): fs-ext is a 14-year-old native addon predating fs-extra; not a typosquat. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is a native addon dependency used via binding.gyp/node-gyp, not imported via require(); false positive for native modules. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 1 / 1 |
v2.1.1
2 findings
HIGH
Package has 'install' script
install-scripts
Script: node-gyp configure build
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.