snappy
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:prebuild-install | AI (phantom-deps): prebuild-install is a known implicit runtime/binary dependency for native addons; not directly imported in JS but used at install time. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is a native addon helper used by node-gyp at compile time, not directly imported in JS — expected for this native binding package. | ai | |
| phantom-deps | phantom-dep:node-gyp | AI (phantom-deps): node-gyp is a known implicit build-time dependency for native addons; not directly imported in JS by design. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp rebuild is the standard install script for native Node.js addons; snappy is a C++ binding and this pattern is stable across all its versions. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-android-arm64 | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-linux-arm64-musl | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-win32-arm64-msvc | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-linux-arm-gnueabihf | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-darwin-x64 | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-freebsd-x64 | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-darwin-arm64 | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-linux-x64-gnu | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-linux-x64-musl | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-win32-x64-msvc | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-linux-arm64-gnu | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| phantom-deps | phantom-dep:@napi-rs/snappy-win32-ia32-msvc | AI (phantom-deps): Platform-specific binary declared as optionalDependency; standard NAPI-RS pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): createRequire/dynamic require is the standard napi-rs mechanism for loading platform-specific optional dependency binaries. Stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): napi-rs loader uses execSync for platform detection to select the correct prebuilt .node binary. Benign and stable for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): napi-rs loader pattern in index.js; child_process is used to detect platform/libc for selecting prebuilt binaries. Stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 7.3.3 | 0 / 18 | |
| 7.3.2 | 0 / 18 | |
| 7.3.1 | 0 / 19 | |
| 7.3.0 | 0 / 19 | |
| 7.2.2 | 13 / 22 | |
| 7.2.1 | 13 / 22 | |
| 7.2.0 | 13 / 22 | |
| 7.1.2 | 13 / 22 | |
| 7.1.1 | 13 / 21 | |
| 7.1.0 | 13 / 20 | |
| 7.0.5 | 13 / 20 | |
| 7.0.4 | 13 / 20 | |
| 7.0.3 | 13 / 18 | |
| 7.0.2 | 13 / 18 | |
| 7.0.1 | 13 / 18 | |
| 7.0.0 | 13 / 18 | |
| 6.3.4 | 3 / 8 | |
| 6.3.2 | 3 / 8 | |
| 6.2.3 | 3 / 7 | |
| 6.2.0 | 3 / 7 | |
| 6.0.0 | 3 / 5 |
v7.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.4
2 findingsScript: prebuild-install || node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.2
2 findingsScript: prebuild-install || node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.3
2 findingsScript: prebuild-install || node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
2 findingsScript: prebuild-install || node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
2 findingsScript: node-gyp rebuild
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.