lzma-native
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 prebuild loader for native addons; stable for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt native binaries for liblzma across platforms; expected for a native binding package. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is used at build time via gyp, not imported in JS; stable false positive. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 8.0.6 | 3 / 4 |
v8.0.6
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • deps/bin_i686/liblzma.dll • deps/bin_x86-64/liblzma.dll • prebuilds/win32-ia32/liblzma.dll • prebuilds/win32-x64/liblzma.dll • prebuilds/darwin-arm64/electron.napi.node • prebuilds/darwin-x64/electron.napi.node • prebuilds/linux-arm64/electron.napi.node • prebuilds/linux-x64/electron.napi.node • prebuilds/win32-ia32/electron.napi.node • prebuilds/win32-x64/electron.napi.node ... and 6 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.