backfill-cache
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:@lage-run/globby | AI (dependencies): Same @lage-run org as the package itself (microsoft/lage monorepo); first-party dependency. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft-maintained package in the lage monorepo; dormancy reflects project cadence, not account takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep @lage-run/globby is the lage project's own scoped fork replacing globby; consistent with internal consolidation. | ai | |
| dependencies | unvetted-dep:backfill-config | AI (dependencies): backfill-config is a sibling package in the same Microsoft/lage monorepo; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.12.5 | 8 / 4 | |
| 5.12.4 | 8 / 4 | |
| 5.12.3 | 8 / 4 | |
| 5.12.2 | 8 / 4 | |
| 5.12.1 | 8 / 4 | |
| 5.12.0 | 8 / 4 | |
| 5.11.4 | 8 / 4 | |
| 5.11.3 | 8 / 9 | |
| 5.11.2 | 8 / 9 | |
| 5.11.1 | 8 / 9 | |
| 5.11.0 | 8 / 9 | |
| 5.10.1 | 9 / 9 |
v5.12.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.