@builder.io/sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 3 / 34 | |
| 6.2.1 | 3 / 34 | |
| 6.2.0 | 3 / 34 | |
| 6.1.3 | 3 / 34 | |
| 6.1.2 | 3 / 34 | |
| 6.1.1 | 3 / 34 | |
| 6.1.0 | 3 / 34 |
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.