fs-native-extensions
Native file system extensions for advanced file operations
Supply chain provenance
Status for the latest visible version.
Maintainers
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): fs-native-extensions is a legitimate native addon from holepunchto; prebuilt .bare binaries for multiple platforms are its documented distribution mechanism, backed by SLSA provenance attestation. | ai | |
| dependencies | unvetted-dep:require-addon | AI (dependencies): require-addon is a holepunchto utility for loading native addons; its use here is expected and consistent with this package's purpose. | ai | |
| dependencies | unvetted-dep:which-runtime | AI (dependencies): which-runtime is a holepunchto utility for detecting the JS runtime (Node vs Bare); its use here is expected for cross-runtime native addon loading. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 2 / 14 | |
| 1.4.5 | 2 / 13 | |
| 1.4.4 | 2 / 13 | |
| 1.4.3 | 2 / 10 |
v1.5.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/fs-native-extensions.bare • prebuilds/android-arm64/fs-native-extensions.bare • prebuilds/android-ia32/fs-native-extensions.bare • prebuilds/android-x64/fs-native-extensions.bare • prebuilds/darwin-arm64/fs-native-extensions.bare • prebuilds/darwin-x64/fs-native-extensions.bare • prebuilds/ios-arm64-simulator/fs-native-extensions.bare • prebuilds/ios-arm64/fs-native-extensions.bare • prebuilds/ios-x64-simulator/fs-native-extensions.bare • prebuilds/linux-arm64/fs-native-extensions.bare ... and 13 more
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.