@sanity/descriptors
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 1 / 17 | |
| 1.2.1 | 1 / 17 | |
| 1.2.0 | 1 / 17 | |
| 1.1.1 | 1 / 17 | |
| 1.1.0 | 1 / 17 | |
| 1.0.0 | 1 / 17 |
v1.3.0
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.