@lage-run/cache-github-actions
Github Action Cache for Lage
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Microsoft/lage uses GitHub Actions CI for publishing; SLSA attestation confirms legitimate automated pipeline, not account compromise. | ai | |
| dependencies | unvetted-dep:@actions/cache | AI (dependencies): @actions/cache is the official GitHub Actions cache package from the actions org; legitimate dependency for a GitHub Actions cache integration. | ai | |
| dependencies | unvetted-dep:backfill-config | AI (dependencies): backfill-config is part of the Microsoft backfill build caching ecosystem, a legitimate dependency for this lage cache package. | ai | |
| dependencies | unvetted-dep:backfill-logger | AI (dependencies): backfill-logger is part of the Microsoft backfill ecosystem; legitimate dependency for this lage cache package. | ai | |
| dependencies | unvetted-dep:workspace-tools | AI (dependencies): workspace-tools is a Microsoft monorepo utility used throughout the lage ecosystem; legitimate dependency. | ai | |
| phantom-deps | phantom-dep:backfill-logger | AI (phantom-deps): backfill-logger is a legitimate Microsoft package referenced in config files; phantom dep finding is a minor code hygiene issue, not a security concern. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.1.41 | 4 / 1 | |
| 0.1.40 | 4 / 1 | |
| 0.1.39 | 4 / 1 | |
| 0.1.38 | 4 / 1 | |
| 0.1.37 | 4 / 1 | |
| 0.1.36 | 4 / 1 | |
| 0.1.35 | 4 / 1 | |
| 0.1.34 | 4 / 1 | |
| 0.1.33 | 4 / 1 | |
| 0.1.32 | 4 / 1 | |
| 0.1.31 | 4 / 1 | |
| 0.1.30 | 4 / 1 | |
| 0.1.29 | 4 / 1 | |
| 0.1.28 | 4 / 1 | |
| 0.1.27 | 4 / 1 | |
| 0.1.26 | 4 / 1 | |
| 0.1.25 | 4 / 1 | |
| 0.1.24 | 4 / 1 | |
| 0.1.23 | 4 / 1 | |
| 0.1.22 | 4 / 1 | |
| 0.1.21 | 4 / 1 | |
| 0.1.20 | 4 / 1 | |
| 0.1.19 | 4 / 1 | |
| 0.1.18 | 4 / 1 | |
| 0.1.17 | 4 / 1 | |
| 0.1.16 | 4 / 1 | |
| 0.1.15 | 4 / 1 | |
| 0.1.14 | 4 / 1 | |
| 0.1.13 | 4 / 1 | |
| 0.1.12 | 4 / 1 | |
| 0.1.11 | 4 / 1 | |
| 0.1.10 | 4 / 1 | |
| 0.1.9 | 4 / 1 | |
| 0.1.8 | 4 / 1 | |
| 0.1.7 | 4 / 1 |
v0.1.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.24
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ecraig12345_msft) than the most recent previously approved version (kenotron_msft) on 2025-04-17, but ecraig12345_msft is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
2 findingsThis version was published by a different npm account (ecraig12345_msft) than the most recent previously approved version (kenotron_msft) on 2023-04-06. It has since remained available on npm for 1201 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.