@graphql-mesh/string-interpolation
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.5.18 | 4 / 0 | |
| 0.5.17 | 4 / 0 | |
| 0.5.16 | 4 / 0 | |
| 0.5.15 | 4 / 0 | |
| 0.5.14 | 4 / 0 | |
| 0.5.13 | 4 / 0 | |
| 0.5.12 | 4 / 0 | |
| 0.5.11 | 4 / 0 | |
| 0.5.10 | 4 / 0 | |
| 0.5.9 | 4 / 0 | |
| 0.5.8 | 4 / 0 | |
| 0.5.7 | 4 / 0 | |
| 0.5.6 | 3 / 0 | |
| 0.5.5 | 3 / 0 | |
| 0.5.4 | 3 / 0 |
v0.5.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.