Collection
Escape Hatch Online · local processing

A–01 Migration inspection tool

Know what survived the import.

Compare a Postman collection with its Bruno or Hoppscotch export. Get a field-level loss report before your team changes clients.

Install the CLI Inspect a sample
cargo install --path .
Blueprint drawing of two document stacks passing through an inspection gate and emerging as a checked report
FIG. 1 Source artifacts pass through a neutral structural inspection. No requests leave the machine.

B–02 Inspection sequence

A migration check you can repeat.

One read-only pass turns “the import looked okay” into a reviewable artifact.

  1. 01

    Point at both sides

    Use your original Postman v2.1 export and the Bruno directory or Hoppscotch JSON produced by the import.

  2. 02

    Measure the structure

    Requests are matched by folder path and name. Critical fields, scripts, examples, variables, and body bytes are compared.

  3. 03

    Keep the evidence

    Commit the Markdown report for review or gate a migration fixture in CI with stable JSON and explicit exit codes.

C–03 Field schedule

Checks what teams actually lose.

Every finding carries a stable code, severity, artifact path, and redacted evidence.

ArtifactMeasurementLoss level
RequestsPath · method · URLCritical
BodiesMode · serialized bytesCritical
AuthEffective type · inheritanceCritical
ScriptsEvent · scope · line countCritical
ExamplesName · status · body bytesCritical
VariablesName · scope · secret stateRedacted

D–04 Local inspection bench

See a lossy import get caught.

This browser preview reads files in memory and makes no network calls. The CLI performs the full comparison.

No source selected
No target selected

Files never leave this tab. Values are not rendered or stored.

REPORT / 001

Inspection report

Awaiting input

No measurement yet.
Load the sample or choose two exports to begin.

RECORDED RUN / 00:07

What a CI run looks like

$ escape-hatch verify --source team.json --target imported.json --json

E–05 Put it in the checklist

One binary. No account.

Build locally today; release archives can carry the same binary later.

migration-check.shread only
$ cargo install --path .

$ escape-hatch verify \
  --source team.postman_collection.json \
  --target bruno/ \
  --format markdown \
  --output migration-report.md

✓ values: [redacted]
! wrote migration-report.md

F–06 Before the team switches

Make the silent loss visible.

Export both sides, run one local command, and review the evidence with the people who own the workflows.

Get the verifier