contentful-resolve-response
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 18 | |
| 1.9.9 | 1 / 18 | |
| 1.9.8 | 1 / 18 | |
| 1.9.7 | 1 / 18 | |
| 1.9.6 | 1 / 18 | |
| 1.9.5 | 1 / 18 | |
| 1.9.4 | 1 / 17 | |
| 1.9.3 | 1 / 17 |
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.