Platform Matrix Scanner: Predicting Where Builds Will Break

The Platform Matrix Scanner collects platform and architecture signals that predict where builds will break. It runs as part of a normal scan and contributes to your DriftScore. This article is for platform engineers and developers who ship across operating systems, runtimes, or CPU architectures.

What it detects

The scanner gathers signals about the platforms and architectures your project targets and depends on, building a matrix that highlights combinations likely to fail. These signals come from the dependencies, configuration, and structure of your project, so the matrix reflects real constraints rather than assumptions.

Why it matters

Build breakage rarely happens on the machine where code was written. It happens on a different OS, a different CPU architecture, or a different runtime version in CI or production. Cross-platform risk is invisible until the matrix expands — a new ARM runner, a Windows target, a newer Node — and then it surfaces as a confusing failure. Collecting platform signals up front lets you predict these failures and test for them deliberately.

For leaders, the matrix shows how portable the portfolio actually is. For developers, it points at the platform combinations that need explicit coverage before they cause an incident.

How to act

Scan the project:

vg

Review the platform matrix and identify combinations flagged as risky. Make sure your CI exercises each platform you ship to, and pay special attention to native modules and platform-specific dependencies that drive most matrix failures. When you add a new target platform, re-scan to see the new risk surface.

Gate on drift in your pipeline:

vg scan --fail-on error

Triage tips

• Expand CI to cover every platform the matrix flags as risky.
• Cross-reference matrix risk with Dependency Risk findings on native modules.
• Re-scan whenever you add a new OS, architecture, or runtime target.

Related

This scanner works hand in hand with the Dependency Risk Scanner (native and platform-specific packages) and the Build & Deploy Scanner. See the CI Integration guides for wiring multi-platform builds.