bare-channel
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): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with holepunchto org automation pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): kasperisager removed as part of shift to automated CI publishing under holepunchto org; not a hostile takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI automation adoption; no malicious indicators present. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Legitimate native addon shipping prebuilt binaries for multiple platforms; standard pattern for bare/holepunchto packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.2.4 | 3 / 5 | |
| 5.2.3 | 3 / 4 | |
| 5.2.2 | 3 / 4 | |
| 5.2.1 | 3 / 4 | |
| 5.2.0 | 3 / 4 | |
| 5.1.6 | 2 / 4 | |
| 5.1.5 | 2 / 4 | |
| 5.1.4 | 2 / 4 | |
| 5.1.3 | 2 / 4 | |
| 5.1.2 | 2 / 4 | |
| 5.1.1 | 2 / 4 | |
| 5.0.5 | 3 / 4 | |
| 5.0.4 | 3 / 4 | |
| 5.0.3 | 3 / 4 | |
| 5.0.2 | 3 / 4 |
v5.2.4
2 findingsThis version was published by a different npm account than previous versions on 2026-06-05. 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.
v5.2.3
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-channel.bare • prebuilds/android-arm64/bare-channel.bare • prebuilds/android-ia32/bare-channel.bare • prebuilds/android-x64/bare-channel.bare • prebuilds/darwin-arm64/bare-channel.bare • prebuilds/darwin-x64/bare-channel.bare • prebuilds/ios-arm64-simulator/bare-channel.bare • prebuilds/ios-arm64/bare-channel.bare • prebuilds/ios-x64-simulator/bare-channel.bare • prebuilds/linux-arm64/bare-channel.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.