@lage-run/cache
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): Transition to GitHub Actions publisher is consistent with CI/CD automation; backed by SLSA provenance attestation for this Microsoft-owned package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a sibling @lage-run monorepo package; routine internal refactor, not a third-party injection. | ai | |
| dependencies | unvetted-dep:backfill-config | AI (dependencies): backfill-config is a Microsoft build caching library, a core dependency of the lage build tool ecosystem. | ai | |
| dependencies | unvetted-dep:backfill-logger | AI (dependencies): backfill-logger is a Microsoft build caching library, a core dependency of the lage build tool ecosystem. | ai | |
| dependencies | unvetted-dep:@lage-run/config | AI (dependencies): Sibling package within the microsoft/lage monorepo; expected internal dependency. | ai | |
| dependencies | unvetted-dep:glob-hasher | AI (dependencies): glob-hasher is a Microsoft/lage ecosystem dependency used for file hashing; part of the same trusted project family. | ai | |
| dependencies | unvetted-dep:@lage-run/target-graph | AI (dependencies): Sibling package within the microsoft/lage monorepo; expected internal dependency. | ai | |
| phantom-deps | phantom-dep:glob-hasher | AI (phantom-deps): glob-hasher is a legitimate Microsoft ecosystem dep; phantom-dep finding is a minor code quality note, not a security concern. | ai | |
| dependencies | unvetted-dep:@lage-run/logger | AI (dependencies): Sibling package within the microsoft/lage monorepo; expected internal dependency. | ai | |
| dependencies | unvetted-dep:backfill-cache | AI (dependencies): backfill-cache is a Microsoft build caching library, a core dependency of the lage build tool ecosystem. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 1.6.5 | 9 / 5 | |
| 1.6.4 | 9 / 5 | |
| 1.6.3 | 9 / 5 | |
| 1.6.2 | 9 / 5 | |
| 1.6.1 | 9 / 5 | |
| 1.6.0 | 9 / 5 | |
| 1.5.5 | 9 / 4 | |
| 1.5.4 | 9 / 4 | |
| 1.5.3 | 9 / 4 | |
| 1.5.2 | 9 / 4 | |
| 1.5.1 | 9 / 4 | |
| 1.5.0 | 9 / 4 | |
| 1.4.12 | 9 / 4 | |
| 1.4.11 | 9 / 2 | |
| 1.4.10 | 9 / 2 | |
| 1.4.9 | 9 / 2 | |
| 1.4.8 | 9 / 2 | |
| 1.4.7 | 9 / 2 | |
| 1.4.6 | 9 / 2 | |
| 1.4.5 | 9 / 2 | |
| 1.4.4 | 9 / 2 | |
| 1.4.3 | 9 / 2 | |
| 1.4.2 | 9 / 2 | |
| 1.4.1 | 9 / 2 | |
| 1.4.0 | 9 / 2 | |
| 1.3.17 | 8 / 2 | |
| 1.3.16 | 8 / 2 | |
| 1.3.15 | 8 / 2 | |
| 1.3.14 | 8 / 2 | |
| 1.3.13 | 8 / 2 | |
| 1.3.12 | 7 / 2 | |
| 1.3.11 | 7 / 2 | |
| 1.3.10 | 7 / 2 | |
| 1.3.9 | 7 / 2 | |
| 1.3.8 | 7 / 2 | |
| 1.3.7 | 7 / 2 | |
| 1.3.6 | 7 / 2 | |
| 1.3.5 | 7 / 2 | |
| 1.3.4 | 7 / 2 | |
| 1.3.3 | 7 / 2 | |
| 1.3.2 | 7 / 2 | |
| 1.3.1 | 7 / 2 | |
| 1.3.0 | 7 / 2 | |
| 1.2.0 | 7 / 2 | |
| 1.1.7 | 6 / 2 | |
| 1.1.6 | 6 / 2 | |
| 1.1.5 | 6 / 2 | |
| 1.1.4 | 6 / 2 | |
| 1.1.3 | 6 / 2 | |
| 1.1.2 | 6 / 2 | |
| 1.1.1 | 6 / 2 |
v1.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.12
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.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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 (kenotron_msft) than the most recent previously approved version (ecraig12345_msft) on 2024-06-10, but kenotron_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.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.