#031Guide4 min

Understand items marked To fix

Read the evidence behind a To fix finding and turn it into a reviewed, verifiable correction.

Hackaiz team · updated 21/11/2026

Illustration: a team reads a security report and marks priorities.
Illustration: a team reads a security report and marks priorities. Illustrative photo, not a screenshot.

01What To fix tells you

In a Hackaiz report, To fix identifies a finding that needs corrective work. It sits between Danger and To watch in the customer-facing severity vocabulary. It is not a statement that your application has already been attacked, and it does not mean that every item with this label has the same business impact. Two findings can share the label while affecting different data, permissions or parts of your application.

Severity and confidence answer separate questions. Severity describes the seriousness of the reported weakness; High confidence, Medium confidence or Low confidence describes the strength of the detection. Read both before scheduling work. A To fix item with weak supporting evidence needs investigation, not an automatic production change. A well-supported item affecting a key workflow deserves a concrete correction plan rather than being left indefinitely because it is not marked Danger.

02Read the finding before choosing a change

Open Projects, select the affected project and open the finding from its list. The detail page separates What was found, Why does it matter?, What should you do next? and Evidence. Start with the location and the analyzed version: a file in a repository and an address tested on a website are different kinds of observation. A website finding may have a tested address instead of a source-code line; this is not a missing file you need to recreate.

Use Evidence to connect the explanation to the exact behavior or code involved. For example, a dependency finding should be considered alongside the package and affected version shown, whereas an access-control finding needs an explanation of which user can reach which resource. These are examples of how to read a result, not a promise that every report contains these issues. If a secret is involved, its masked value is deliberate; do not paste the complete credential into a discussion.

  1. 1Check the project and analyzed version before editing anything.
  2. 2Read the explanation and Evidence together, then inspect the indicated location.
  3. 3Identify the behavior that must stop and the legitimate behavior that must continue.

03Define a correction that preserves the application

Turn the finding into a small, testable task. For an authorization issue, a useful acceptance condition is that an unauthorized account is denied access while the permitted account can still complete its work. For a vulnerable dependency, inspect the suggested fixed version when present and check compatibility before updating. Changing a version number without exercising the affected application path is not the same as validating a safe release.

Where a GitHub correction is available, Hackaiz prepares a proposal for human review. Fixes are draft GitHub pull requests, not changes silently merged into your main branch. Review the proposed files and tests, approve publication only after inspecting the proposal, and let a person decide whether to merge. The Corrections screen helps you follow this work. A proposal is not proof that the deployed application is already repaired, and an exposed secret may also require revocation with its provider.

04Check the result, not only the merged code

After review and deployment, verify the affected behavior on the intended version. The finding detail can offer a replay or a test when supporting evidence is available; use those instructions only within your authorized environment. A new analysis can check whether the original evidence remains. Analysis uses credits, so select the relevant checks deliberately. Unticked checks are neither run nor billed; a test you did not select cannot validate the correction.

Keep the distinction between applied and verified visible in your handover. A merged pull request means repository content changed; it does not establish that production received that change or that all access paths are protected. If the result is still uncertain, record what was actually checked and what remains to investigate. Do not report the whole application as secure because one To fix item no longer appears.

Frequently asked questions

Was this article helpful?

Related articles