Browser replay

One recorded scan of a synthetic image.

Simulated demo

Nothing is scanned in your browser. The transcript is the real output of layerleak scan run against a local OCI image layout whose secrets are fabricated at test time, and the tables are the rows PostgreSQL would hold for that result, derived with the same record builder the CLI and API use. Only the clock, the record name's random suffix and the working directory are pinned. Raw storage is off, so the raw-value columns are empty, as they are by default.

Example command
loading demo fixture...

The layout holds one multi-platform index tagged 1.4.2. Without --platform only its linux/amd64 image is scanned; the windows/amd64 image and the attestation manifest are reported as platform_skipped and manifest_skipped diagnostics. The scan exits 2 because it found actionable findings.

Status: waiting to replay

        
Local snapshot

Result, coverage and the scan record the CLI wrote.

Status

Awaiting replay

Coverage

Awaiting replay

Actionable findings

Awaiting replay

Diagnostics

Awaiting replay

Scan record

Awaiting replay

Postgres-style rows derived from the result

layerleak tables after the replayed run

Run the replay to load rows
Run the replay to load the Postgres-style rows.