bare-signals
Native signal handling for JavaScript
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Native addon package; prebuilds are expected and source code (binding.c, CMakeLists.txt) is included alongside them. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 2 / 4 | |
| 4.1.0 | 2 / 4 | |
| 4.0.5 | 2 / 4 | |
| 4.0.4 | 2 / 4 | |
| 4.0.3 | 2 / 4 |
v4.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-signals.bare • prebuilds/android-arm64/bare-signals.bare • prebuilds/android-ia32/bare-signals.bare • prebuilds/android-x64/bare-signals.bare • prebuilds/darwin-arm64/bare-signals.bare • prebuilds/darwin-x64/bare-signals.bare • prebuilds/ios-arm64-simulator/bare-signals.bare • prebuilds/ios-arm64/bare-signals.bare • prebuilds/ios-x64-simulator/bare-signals.bare • prebuilds/linux-arm64/bare-signals.bare ... and 3 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.