> ## Documentation Index
> Fetch the complete documentation index at: https://qodex.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# What do I do about false positives?

> Mark incorrect findings as false positives and use Qodex evidence, deduplication, and status tracking to keep triage clean.

# What do I do about false positives?

If a finding is wrong, mark it as a false positive.

Qodex keeps the finding so the item stays out of the default open list while remaining searchable for audit and history.

![Qodex failure analysis view used during finding review and triage](https://mintcdn.com/qodexai/rhkO1RmGEPTQ07wr/images/docs/findings/failure-analysis.png?fit=max\&auto=format\&n=rhkO1RmGEPTQ07wr\&q=85\&s=30652d9863dd79e98f2b9e0eace20bb1)

## Before a finding reaches you

Qodex applies guards to reduce common false positives:

| Guard | What it catches |
| - | - |
| Misanchor guard | PR findings attached to imports, comments, blank lines, or structural lines. |
| Evidence guard | High-severity claims without enough screenshot, DOM, request, or response evidence. |
| Deduplication | Repeated observations of the same open issue. |
| Rule check | Access-control claims with no rule, endpoint note, or statement from you behind them. These are held as **Needs review** instead of being filed. |

These guards reduce noise, but reviewers should still triage findings.

## Mark a false positive

Open **Findings**, click the finding, and under **Mark as** click **False positive**.

The finding remains in history, but it no longer appears in the default open list. To see it again, add **False positive** in the **Status** filter.

For a finding in **Needs review**, click **Dismiss** under **Waiting for you**. That closes it as a false positive and records who decided.

A code scan finding you mark as false positive or won't fix is not filed again on the next scan.

## False positive vs won't fix

Use **False positive** when Qodex is wrong.

Use **Won't fix** when Qodex is right but your team intentionally accepts the risk or chooses not to change the behavior.

If the finding is real but rated too high or too low, keep it open and change its severity under **Review** instead, with a note saying why.

## PR review notes

Inline PR findings can occasionally be advisory when the anchor is uncertain. Review the surrounding code and evidence before treating the finding as confirmed.

## Next steps

> [card] [Inline findings](https://qodex.ai/docs/pr-review-inline-findings.md)
>
> See how PR comments are anchored.

> [card] [Slash commands](https://qodex.ai/docs/pr-review-slash-commands.md)
>
> Learn the current PR command surface.

> [card] [Findings](https://qodex.ai/docs/concepts-findings.md)
>
> Understand Qodex findings.

> [card] [Triage workflow](https://qodex.ai/docs/findings-triage-workflow.md)
>
> Move findings through review.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.