@contrast/distringuish
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
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 prebuilt-binary loader for native addons; stable pattern for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries are expected for a native addon package from Contrast Security; consistent across versions. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is a native addon build dependency referenced in binding config, not imported in JS — stable false positive. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a native addon build dependency referenced in binding config, not imported in JS — stable false positive. | ai |
v6.0.2
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/linux-arm64/@contrast+distringuish.abi108.armv8.node • prebuilds/linux-x64/@contrast+distringuish.abi108.glibc.node • prebuilds/linux-x64/@contrast+distringuish.abi108.musl.node • prebuilds/win32-x64/@contrast+distringuish.abi108.node • prebuilds/linux-arm64/@contrast+distringuish.abi115.armv8.node • prebuilds/linux-x64/@contrast+distringuish.abi115.glibc.node • prebuilds/linux-x64/@contrast+distringuish.abi115.musl.node • prebuilds/win32-x64/@contrast+distringuish.abi115.node • prebuilds/linux-arm64/@contrast+distringuish.abi127.armv8.node • prebuilds/linux-x64/@contrast+distringuish.abi127.glibc.node ... and 6 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.