fuse-native
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
andrewoshmafintosh
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): node-gyp-build is the standard native addon install pattern for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries are expected for a native FUSE binding; consistent with prebuildify workflow. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for FUSE mount/unmount operations; expected for this native binding package. | ai | |
| phantom-deps | phantom-dep:napi-macros | AI (phantom-deps): napi-macros is referenced in C/gyp build config, not JS imports; stable false positive for native addons. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.2.6 | 4 / 4 |
v2.2.6
3 findings
HIGH
Package has 'install' script
install-scripts
Script: node-gyp-build
HIGH
Bundled binary files (5)
npm-metadata
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-x64/electron.napi.node • prebuilds/linux-x64/electron.napi.node • prebuilds/darwin-x64/node.napi.node • prebuilds/linux-x64/node.napi.node • prebuilds/linux-x64/libfuse.so
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.