@glimmer/reference
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@glimmer/validator | AI (dependencies): Sibling package from the same glimmer-vm monorepo; unvetted status is a pipeline gap, not a security risk. | ai | |
| dependencies | unvetted-dep:@glimmer/global-context | AI (dependencies): Sibling package from the same glimmer-vm monorepo; unvetted status is a pipeline gap, not a security risk. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.94.9 | 4 / 7 | |
| 0.94.8 | 4 / 7 | |
| 0.94.7 | 4 / 7 | |
| 0.94.6 | 4 / 7 | |
| 0.94.5 | 4 / 7 | |
| 0.94.4 | 4 / 7 | |
| 0.94.3 | 4 / 7 | |
| 0.94.2 | 4 / 7 | |
| 0.94.1 | 4 / 7 | |
| 0.94.0 | 4 / 7 | |
| 0.93.1 | 5 / 7 | |
| 0.93.0 | 5 / 7 | |
| 0.92.3 | 5 / 6 | |
| 0.92.2 | 5 / 6 |
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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. 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.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.