#052Tutorial3 min

Audit an app built with Bolt

Choose the deployed address and repository that represent your Bolt application, then review the evidence.

Hackaiz team · updated 21/11/2026

Illustration: a founder builds an AI app.
Illustration: a founder builds an AI app. Illustrative photo, not a screenshot.

01Identify the app you actually want to test

For a Bolt application, distinguish the published website from the source project used to build it. The website shows what the deployed version exposes; a connected GitHub repository gives Hackaiz code to inspect. A site address does not grant access to private source files, and a repository is not proof that its latest commit is already deployed. Before starting, note the intended hostname and repository. If you have a preview and a production version, decide which one you are authorizing rather than treating them as interchangeable.

Use the Connect screen to choose the address-based path or the connected-system path. For source analysis, use Connect GitHub and select an authorized repository in Choose a repository to scan. Do not select an unrelated demonstration repository just because it uses the same framework. If your Bolt source is not available through an authorized GitHub repository, do not assume Hackaiz can read the editor workspace directly. The connected repository and the published address are the concrete analysis inputs described here.

02Prove control before testing the published site

Website and API analysis require domain ownership proof. The accepted choices are a DNS TXT record named _hackaiz, an HTTPS file at /.well-known/hackaiz-verification.txt, or asking the AI that edits the project to create that file with Hackaiz’s instruction. For Bolt, the listed file location in the project is public/.well-known/hackaiz-verification.txt. Use the exact value displayed by Hackaiz. Creating a file in the editor is not enough if it has not been included in the published version served at the selected domain.

Check the intended address and publish your change through your usual Bolt workflow. A proof for a preview hostname should not be treated as proof for your production domain. If you manage the custom domain’s DNS, the TXT method is another option. Do not bypass verification by changing the description of the analysis: Hackaiz does not analyze websites or APIs without proof. Once the right resource is selected, inspect the selected checks. Analysis consumes credits, and checks you untick are neither executed nor billed.

03Read generated-code risks as specific findings

A working generated interface is not evidence that every authorization and secret-handling decision is correct. Repository checks include database queries assembled from variable text, risky dynamic execution, AI provider keys exposed through public browser variables, and shell commands built from variables. For example, a key referenced through VITE_OPENAI_API_KEY can end up available to visitors. The relevant repair is to keep the privileged call and key on the server, not to hide the input field in the interface. These examples describe supported patterns, not findings guaranteed to exist in every Bolt app.

Customer levels are Danger, To fix, and To watch. Read the affected file, evidence, and next action before asking Bolt to rewrite anything. Give the coding assistant a focused requirement and remove secrets from copied context. If a repository proposal is appropriate, Hackaiz prepares a draft GitHub pull request after approval for publication; a human reviews and decides on merging. No automatic merge occurs. Recheck the version actually deployed after the repair: a clean rescan alone does not verify a correction, which also needs replay, passing tests, and matching deployment evidence.

Frequently asked questions

Was this article helpful?

Related articles