Triage & Analysis - Binarly Transparency Platform

Effective triage involves comparing scanned binary file versions to spot regressions and analyzing individual findings for root cause analysis.

1. Regressions (Compare Images)

To identify what changed between two versions (e.g., a “Golden Master” vs. a new Release Candidate), use the comparison feature.

Workflow

Identify the Baseline Image ID (e.g., previous stable version).
Identify the Target Image ID (e.g., new build).
Use the findings:gridList endpoint to filter by comparison IDs.

# Compare Baseline (Left) vs Target (Right)
curl -sS --fail-with-body -X POST \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "filters": [
      {"field": "compareLeftImageId", "value": "'"$BASELINE_IMAGE_ID"'", "comparator": "equals"},
      {"field": "compareRightImageId", "value": "'"$TARGET_IMAGE_ID"'", "comparator": "equals"}
    ],
    "page": {"num": 1, "size": 100}
  }' \
  "${BINARLY_API_URL}/api/v4/grids/findings:gridList"

The response returns up to 100 findings per page (10 without page). The total field holds the number of findings across all pages. To split the results, add a compareSide filter, for example {"field": "compareSide", "value": "right", "comparator": "equals"}:

`compareSide`	Findings
`left`	Only in the baseline image (resolved)
`right`	Only in the target image (new)
`both`	In both images (unchanged)

2. Analyze Findings

Once you identify a critical finding, retrieve its full details.

Get the finding id from the comparison results.
Retrieve the finding with GET /api/v4/products/{productId}/findings/{findingId}:

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  "${BINARLY_API_URL}/api/v4/products/${BINARLY_PRODUCT_ID}/findings/$FINDING_ID"

User Guides

Compare Images - UI walkthrough for comparing firmware versions