@glimmer/manager
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.94.10 | 7 / 8 | |
| 0.94.9 | 7 / 8 | |
| 0.94.8 | 7 / 8 | |
| 0.94.7 | 7 / 8 | |
| 0.94.6 | 7 / 8 | |
| 0.94.5 | 7 / 8 | |
| 0.94.4 | 7 / 8 | |
| 0.94.3 | 7 / 8 | |
| 0.94.2 | 7 / 8 | |
| 0.94.1 | 7 / 8 | |
| 0.94.0 | 7 / 8 |
v0.94.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.94.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.94.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.94.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.