@glimmer/global-context
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.93.4 | 0 / 6 | |
| 0.93.3 | 0 / 6 | |
| 0.93.2 | 0 / 6 | |
| 0.93.1 | 0 / 6 | |
| 0.93.0 | 0 / 6 | |
| 0.92.4 | 0 / 5 | |
| 0.92.3 | 0 / 5 | |
| 0.92.2 | 0 / 5 | |
| 0.92.1 | 0 / 5 |
v0.93.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.93.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.93.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.