#074Tutorial4 min
Prepare your workspace for Hackaiz
Choose the correct folder, understand exclusions, and keep source selection separate from platform selection.
Hackaiz team · updated 21/11/2026

01Start with the folder you intend to inspect
The editor workspace scan starts from the first open workspace folder. In a window with several roots, do not assume it combines every project into one analysis. Open the relevant application folder before selecting “Hackaiz: Scan this workspace”. For a large repository containing several applications, opening the application you are reviewing makes the file selection easier to understand. This is a practical scope choice, not a claim that the remainder of the repository is safe.
A current-file scan follows a different path: it reads the text of the active local editor document. A workspace scan reads files through the filesystem. Save the changes you want a workspace scan to inspect so that the on-disk files match your intended review. Conversely, when investigating the active file, check that the correct tab is selected. An untitled document or a non-file editor is not a substitute for an eligible source file.
02Understand what the collector leaves out
The workspace collector excludes common folders such as node_modules, .git, dist, build, coverage and .venv. It also filters secret filenames including .env variants, private key and certificate containers, .npmrc and .netrc. Binary files, minified JavaScript or CSS and source maps are excluded. These rules reduce inappropriate submissions, but they are not a promise that every remaining source file is free of sensitive content. Review the material you are authorizing to send.
The implementation also applies file-count, per-file size and total-size limits. If a file is skipped because it is too large or a limit is reached, it is outside that submission. Installing dependencies will not make excluded dependency code part of the workspace scan. For example, a lockfile can describe a dependency while the contents of node_modules remain excluded. Treat skipped paths as a boundary to document, not a positive security result.
- 1Remove unrelated material from the chosen review scope.
- 2Read the submission information and excluded-file reasons.
- 3Use a smaller relevant folder if the original selection is too broad.
03Prepare account access separately from local files
“Hackaiz: Connect personal key” links the extension to your account. The key is stored in VS Code SecretStorage and needs the launch permission for scans. Do not create a .env file containing the key just to make the extension work. “Hackaiz: Choose platform” selects the saved platform associated with the workspace, using hackaiz.projectId. That identifier is not a path filter and does not choose which local files the workspace collector reads.
Similarly, choosing a platform does not prove domain control. If you later analyze a website or API, complete ownership verification in Connect using the _hackaiz DNS TXT record, the HTTPS file at /.well-known/hackaiz-verification.txt, or the project AI instruction that creates that file. An open repository folder and a selected platform are useful context, but neither authorizes an unverified domain or connects an otherwise missing database.
04Confirm a scope you can explain afterward
Every editor scan requires confirmation and uses Hackaiz account credits. Review the intended file submission before approving it, then read the actual charge and completion information in the returned result. If the extension reports that no readable source files are available, check whether the open folder contains only excluded content or whether the current file is ineligible. Renaming a private key to bypass the filter is not a troubleshooting step.
Keep a simple review note: which folder or file was examined, whether you saved the source first, what was skipped and whether the scan completed. If a time limit leaves the result incomplete, review a smaller relevant set rather than describing it as a clean whole-project analysis. Findings can then be investigated at their file and line. Preparing the workspace does not enable automatic repairs: the extension never edits, commits or merges your code.
Frequently asked questions
Take the next step
Was this article helpful?