#075Tutorial4 min
Examine a code file with the available tools
Use the active-file editor scan for source review, and keep it distinct from the CLI component check.
Hackaiz team · updated 21/11/2026

01Select the actual source document
The editor extension implements “Hackaiz: Scan current file”. It is the direct option for reviewing a single local code file without requesting an analysis of a whole saved platform. Open the containing folder, make the intended file the active editor and connect a personal key with launch access. The implementation reads the active document text, so confirm that the visible tab and its current contents are the material you intend to submit.
Use a focused example to set expectations: if a route builds a database query using a request parameter, examine that handler and the code that validates or transforms the parameter. A scan may identify a risky pattern in the submitted file, but a one-file submission does not establish what happens in every caller, middleware layer or database policy. Keep the path and surrounding context available when you review the returned explanation.
02Review the submission before approving it
The same workspace filtering logic applies to the current-file submission. Secret filenames, binary or generated content and oversized files can be rejected. If no readable source remains, the extension warns instead of treating the missing input as a successful review. Do not put a real credential in the file just to test the tool, and do not rename an excluded secret file to make it eligible. Use representative source with sensitive material removed when discussing an example.
A scan is sent only after your confirmation and uses account credits. Once it finishes, check the file coverage and completion information alongside the actual credit charge. A finding-free response and an incomplete response are different states. If another file contains the authorization check relevant to the question, a later focused scan or a deliberate workspace scan can add context, but that is a new operation rather than proof that the original file review covered it.
- 1Activate the local source file you want to inspect.
- 2Run “Hackaiz: Scan current file” and review the confirmation.
- 3Open each relevant result at its file and line, then compare the explanation with nearby code.
03Do not confuse source scanning with component checking
The prepared CLI also has “hackaiz check <path>”, intended for a Skill, MCP configuration, package description, workflow or similar component before installation. It sends collected text to the component-check endpoint and can emit SARIF, a structured format used by code-scanning tools. This is not the same command as the editor active-file scan, and it should not be advertised as a general single-file application audit with identical findings or coverage.
The CLI source is present in tools/hackaiz-cli, but the integration page says the connected client is not published on npm. If you use the source client in a controlled setup, verify its prerequisites rather than assuming a public install command is available. Component checking is static: it does not execute the submitted installation script or prove runtime behavior. The check command returns a failure code for Danger and a separate incomplete code, so do not translate every nonzero exit into the same diagnosis.
04Turn a file finding into a review task
In the editor, results link back to the local path and line, and inline diagnostics can show the issue in the Problems panel. Read the finding title, what was observed, impact and next action before editing. For a suspected injection, the review question is whether untrusted input reaches the sensitive operation safely, not simply whether a suspicious function name appears. The tool provides evidence to investigate; it does not replace understanding the execution path.
The extension never changes the file for you. If a correction is pursued through Hackaiz for an eligible repository finding, it remains a draft GitHub pull request that a person reviews and approves; it is never merged automatically. Testing the corrected behavior and obtaining a relevant later check are separate steps. A local file scan also grants no permission to analyze a live website or API: those targets require verified domain ownership before any analysis.
Frequently asked questions
Take the next step
Was this article helpful?