@expo/template-file
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 20.0.0 | 1 / 8 | |
| 19.0.0 | 1 / 8 | |
| 18.5.0 | 1 / 8 | |
| 18.0.1 | 1 / 7 | |
| 1.0.260 | 1 / 7 | |
| 1.0.252 | 1 / 7 |
v20.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v19.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.260
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.