bare-structured-clone
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; dormancy is explained by infrequent releases for a stable native addon. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Native addon package from Holepunch; prebuilds are expected and covered by SLSA provenance attestation. | ai | |
| dependencies | unvetted-dep:bare-buffer | AI (dependencies): bare-buffer is a Holepunch ecosystem package consistent with this org's native addon dependencies. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.5.5 | 4 / 5 | |
| 1.5.4 | 4 / 5 | |
| 1.5.3 | 2 / 6 | |
| 1.5.2 | 2 / 6 | |
| 1.5.1 | 2 / 6 | |
| 1.5.0 | 2 / 6 | |
| 1.4.3 | 2 / 6 |
v1.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.4
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-structured-clone.bare • prebuilds/android-arm64/bare-structured-clone.bare • prebuilds/android-ia32/bare-structured-clone.bare • prebuilds/android-x64/bare-structured-clone.bare • prebuilds/darwin-arm64/bare-structured-clone.bare • prebuilds/darwin-x64/bare-structured-clone.bare • prebuilds/ios-arm64-simulator/bare-structured-clone.bare • prebuilds/ios-arm64/bare-structured-clone.bare • prebuilds/ios-x64-simulator/bare-structured-clone.bare • prebuilds/linux-arm64/bare-structured-clone.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.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.