@shopify/app-bridge-types
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 1 / 4 | |
| 0.7.1 | 1 / 4 | |
| 0.7.0 | 1 / 2 | |
| 0.5.3 | 1 / 2 | |
| 0.5.2 | 1 / 2 | |
| 0.5.1 | 0 / 3 | |
| 0.5.0 | 0 / 2 | |
| 0.4.0 | 0 / 1 | |
| 0.3.0 | 0 / 1 | |
| 0.2.0 | 0 / 1 | |
| 0.1.0 | 0 / 1 | |
| 0.0.18 | 0 / 1 | |
| 0.0.17 | 0 / 1 | |
| 0.0.16 | 0 / 2 | |
| 0.0.15 | 0 / 2 | |
| 0.0.14 | 0 / 1 |
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.