bare-signals
Native signal handling for JavaScript
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CI/CD migration with SLSA attestation, not account compromise. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with legitimate move to CI-based publishing. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration, not takeover. | ai | |
| 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 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 1 / 6 | |
| 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 | |
| 4.0.2 | 2 / 4 | |
| 4.0.1 | 2 / 4 | |
| 4.0.0 | 2 / 4 |
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.