fswin
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
xxoo
Keywords
nativefsfilesystemwatchwindowswildcardsntfs
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Native Node addon; arch-specific .node binaries are the core deliverable for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves arch-specific native binary path — standard pattern for native addons. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.25.1108 | 0 / 0 |
v3.25.1108
2 findings
HIGH
Bundled binary files (3)
npm-metadata
Package contains compiled binaries that could be backdoors: • arm64/fswin.node • ia32/fswin.node • x64/fswin.node
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.