bare-thread
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): Prebuilt native addon binaries are expected for bare-thread; SLSA provenance confirms legitimate CI/CD build. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 4 / 5 | |
| 1.2.2 | 4 / 5 | |
| 1.2.1 | 3 / 5 | |
| 1.2.0 | 3 / 5 | |
| 1.1.6 | 3 / 3 | |
| 1.1.5 | 3 / 3 | |
| 1.1.4 | 3 / 3 | |
| 1.1.3 | 3 / 3 | |
| 1.1.2 | 3 / 3 | |
| 1.1.1 | 3 / 3 | |
| 1.1.0 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
v1.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-thread.bare • prebuilds/android-arm64/bare-thread.bare • prebuilds/android-ia32/bare-thread.bare • prebuilds/android-x64/bare-thread.bare • prebuilds/darwin-arm64/bare-thread.bare • prebuilds/darwin-x64/bare-thread.bare • prebuilds/ios-arm64-simulator/bare-thread.bare • prebuilds/ios-arm64/bare-thread.bare • prebuilds/ios-x64-simulator/bare-thread.bare • prebuilds/linux-arm64/bare-thread.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.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.