#050Case study1 min

Full walkthrough: from analysis to verified fix

An end-to-end journey, step by step, with what you see on each screen.

Hackaiz team · updated 18/11/2026

Illustration: two developers review a change before approving it.
Illustration: two developers review a change before approving it. Illustrative photo, not a screenshot.

01The starting point

This walkthrough describes, screen by screen, the full path from a published app to a verified fix. It is not a video: a filmed demonstration is planned and will be added once it exists.

021 to 3: connect and analyze

The first three steps set the authorized frame.

  1. 1Prove the domain from Connect (DNS or HTTPS file).
  2. 2Install the GitHub App on the repository and, if needed, link Supabase read-only.
  3. 3From Analyze, keep checks ticked, enter the live address and launch.

034 and 5: read and decide

The report opens with the verdict. Open the first Danger finding, read the evidence and explanation, then decide: fix now, plan it, or flag a doubt.

046 to 8: fix and verify

A fix always goes through human approval.

  1. 1Prepare a fix; it appears as “ready for review”.
  2. 2Review and approve it; a change is proposed on a dedicated GitHub branch.
  3. 3Merge it yourself, deploy, then re-run the analysis from the report to see it gone.

Frequently asked questions

Was this article helpful?

Related articles