#076Guide4 min
Understand a vulnerability in your editor
Follow a finding from its severity group to its source line, evidence and next action without confusing a warning with a fix.
Hackaiz team · updated 21/11/2026

01Locate the finding and its source
After a workspace scan, the Hackaiz extension displays findings in its sidebar and can add underlines and Problems entries to your source files. Click a workspace finding to open the reported path at its line. A warning beside the code is an annotation from a returned result, not a live proof that the code currently running in production has the same behavior. Check which scan produced it and whether you have edited the relevant source since that scan.
The extension also reads findings for a selected saved platform. Those findings may concern a website, an API or a repository connected in Hackaiz, rather than the open local file. Use “Hackaiz: Choose platform” to confirm that context. If a platform finding does not correspond to the local checkout, do not force a match merely because the application names look alike. Local findings and platform history are related information, but they are not interchangeable evidence.
02Read the customer-facing severity groups
The editor groups results under Danger, To fix and To watch. Critical and High technical severities belong to Danger; Medium belongs to To fix; Low and informational findings belong to To watch. The extension may show both the customer label and the technical suffix. Use that grouping to order your reading, then assess the specific finding rather than treating every item in a group as an identical incident.
For example, a secret referenced in source and an input-handling flaw raise different questions. A secret-related finding calls for checking exposure and replacing a real exposed credential through the responsible service. An injection-related finding calls for tracing the source of input and the sensitive operation. The group helps prioritize attention; the written observation and impact explain why this particular location deserves review. Neither the color nor the count establishes complete application coverage.
- 1Start with the Danger group if it contains findings.
- 2Open the exact location and read the observation before planning a change.
- 3Check completion and scope separately from the severity label.
03Use the explanation instead of guessing from the underline
Hovering an underline gives a short diagnostic. In the workspace view, “Show details” opens a fuller explanation with the finding information and masked evidence. Read what was found, the impact and the next action together. Masked evidence is intentionally not a recoverable copy of a credential. Do not paste the unmasked value into a ticket or assistant conversation to make the explanation more precise.
Treat examples in a finding as evidence to compare with the surrounding code. If a reported query is parameterized elsewhere, or if a sensitive action is protected by middleware in another file, identify that path before concluding the finding is confirmed or mistaken. Conversely, a reassuring function name is not evidence that authorization actually occurs. The editor helps you navigate and understand; it does not replace reviewing the complete relevant data flow.
04Choose a safe next action
Use “Hackaiz: Open report and approvals” when the saved-platform context or a correction review needs the web application. The extension does not apply a repair, create a commit or merge a pull request. Eligible Hackaiz corrections are draft GitHub pull requests; a human reviews and approves them, and they are never merged automatically. If you edit manually, inspect the proposed behavior, run the appropriate tests and obtain a relevant later check rather than hiding the diagnostic.
The hackaiz.showInlineDiagnostics setting controls whether findings appear as inline and Problems diagnostics. Turning it off changes display, not finding status. Likewise, the refresh setting retrieves information; it is not proof that a new security analysis was run after your edit. Additional analyses use credits. Keep unresolved questions about excluded files or incomplete processing in the review record so that a quieter editor is not mistaken for a verified correction.
Frequently asked questions
Take the next step
Was this article helpful?