bare-subprocess
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): Native addon package from holepunchto; prebuilt .bare binaries are the documented distribution mechanism for this ecosystem. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 5 / 10 | |
| 5.2.3 | 5 / 9 | |
| 5.2.2 | 5 / 9 | |
| 5.2.1 | 5 / 9 | |
| 5.2.0 | 5 / 9 | |
| 5.1.5 | 5 / 9 |
v6.0.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-subprocess.bare • prebuilds/android-arm64/bare-subprocess.bare • prebuilds/android-ia32/bare-subprocess.bare • prebuilds/android-x64/bare-subprocess.bare • prebuilds/darwin-arm64/bare-subprocess.bare • prebuilds/darwin-x64/bare-subprocess.bare • prebuilds/ios-arm64-simulator/bare-subprocess.bare • prebuilds/ios-arm64/bare-subprocess.bare • prebuilds/ios-x64-simulator/bare-subprocess.bare • prebuilds/linux-arm64/bare-subprocess.bare ... and 3 more
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.3
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-subprocess.bare • prebuilds/android-arm64/bare-subprocess.bare • prebuilds/android-ia32/bare-subprocess.bare • prebuilds/android-x64/bare-subprocess.bare • prebuilds/darwin-arm64/bare-subprocess.bare • prebuilds/darwin-x64/bare-subprocess.bare • prebuilds/ios-arm64-simulator/bare-subprocess.bare • prebuilds/ios-arm64/bare-subprocess.bare • prebuilds/ios-x64-simulator/bare-subprocess.bare • prebuilds/linux-arm64/bare-subprocess.bare ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-subprocess.bare • prebuilds/android-arm64/bare-subprocess.bare • prebuilds/android-ia32/bare-subprocess.bare • prebuilds/android-x64/bare-subprocess.bare • prebuilds/darwin-arm64/bare-subprocess.bare • prebuilds/darwin-x64/bare-subprocess.bare • prebuilds/ios-arm64-simulator/bare-subprocess.bare • prebuilds/ios-arm64/bare-subprocess.bare • prebuilds/ios-x64-simulator/bare-subprocess.bare • prebuilds/linux-arm64/bare-subprocess.bare ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-subprocess.bare • prebuilds/android-arm64/bare-subprocess.bare • prebuilds/android-ia32/bare-subprocess.bare • prebuilds/android-x64/bare-subprocess.bare • prebuilds/darwin-arm64/bare-subprocess.bare • prebuilds/darwin-x64/bare-subprocess.bare • prebuilds/ios-arm64-simulator/bare-subprocess.bare • prebuilds/ios-arm64/bare-subprocess.bare • prebuilds/ios-x64-simulator/bare-subprocess.bare • prebuilds/linux-arm64/bare-subprocess.bare ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-subprocess.bare • prebuilds/android-arm64/bare-subprocess.bare • prebuilds/android-ia32/bare-subprocess.bare • prebuilds/android-x64/bare-subprocess.bare • prebuilds/darwin-arm64/bare-subprocess.bare • prebuilds/darwin-x64/bare-subprocess.bare • prebuilds/ios-arm64-simulator/bare-subprocess.bare • prebuilds/ios-arm64/bare-subprocess.bare • prebuilds/ios-x64-simulator/bare-subprocess.bare • prebuilds/linux-arm64/bare-subprocess.bare ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-subprocess.bare • prebuilds/android-arm64/bare-subprocess.bare • prebuilds/android-ia32/bare-subprocess.bare • prebuilds/android-x64/bare-subprocess.bare • prebuilds/darwin-arm64/bare-subprocess.bare • prebuilds/darwin-x64/bare-subprocess.bare • prebuilds/ios-arm64-simulator/bare-subprocess.bare • prebuilds/ios-arm64/bare-subprocess.bare • prebuilds/ios-x64-simulator/bare-subprocess.bare • prebuilds/linux-arm64/bare-subprocess.bare ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.