endor-troubleshooting-scans

To diagnose an Endor Labs scan regression, compare adjacent scan pairs to rank anomalies, diff aggregate metrics like dependency counts, and search embedded scan logs for failure signatures to isolate the root cause.

A scan reporting fewer dependencies and partial success often indicates a dependency-resolution collapse; you can probe package-version resolution errors and search embedded scan logs to pinpoint the specific resolution failure.

Comparing Endor Labs scans involves resolving the project from an app scan-history URL, selecting a bounded scan-window retrieval, and diffing aggregate metrics such as status, dependency counts, and finding totals.

Yes, you can use an app scan-history URL to resolve projects and apply heuristic recent-run triage to identify the relevant scan window and isolate failure signatures.

Troubleshooting dependency resolution errors requires searching embedded scan logs for failure signatures, applying log fallback handling if needed, and probing package-version resolution errors during metric collapse.

Bounded scan-window retrieval is necessary when diagnosing pipeline regressions on recent runs, ensuring analysis focuses strictly on relevant adjacent scan pairs rather than overwhelming the comparison with unrelated historical data.