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

# Triage findings: fixed, false positive and risk accepted

> How Octopoda finding statuses work, how findings close when a re-test cannot reproduce them, and how to mark a false positive or accept a risk.

Octopoda tracks each finding from the scan that first proved it until it is fixed or you decide not to fix it. This page explains the statuses, what changes them, and how to triage several findings at once.

## Statuses

| Status | Meaning | Set by |
| - | - | - |
| **New** | Proven in the last 7 days. | Octopoda |
| **Open** | Proven more than 7 days ago and not resolved. | Octopoda |
| **Fixed** | A later scan could no longer reproduce it. | Octopoda, after a re-test |
| **False positive** | Someone on your team decided it is not a real issue. | You, with a reason |
| **Risk accepted** | Someone on your team decided not to fix it. | You, with a reason |

A finding that a later scan proves again stays the same finding: its history shows each scan that saw it.

## How findings are re-tested

A full code scan re-tests the findings that are still new or open in the same code, up to 30 per scan:

* a scan of a repository's default branch re-tests that repository's findings;
* a scan from the CLI or an AI tool re-tests the findings from earlier scans of the same project folder, recognized by the folder's name.

Each finding the scan can no longer reproduce is marked **Fixed**, and its page links to that scan. Pull request scans, and scans of other branches, report what they prove but do not close findings. See [Fix a finding with your AI tool](https://docs.octopoda.dev/findings/fix-with-ai.md#when-a-finding-is-marked-fixed).

## Mark a false positive or accept a risk

**1. Open the finding**

Open it from the **Findings** page or a scan.

**2. Choose the status**

Select **Mark as false positive** or **Accept risk with a reason**.

**3. Add a reason**

Write a short reason, such as "Admin-only route behind VPN". The reason and your name are kept in the finding's history and shown on the finding.

Anyone on the team can triage findings. To undo a decision, reopen the finding.

## Triage several findings at once

On the **Findings** page, select the findings with their checkboxes, then choose a status for all of them. The same reason is recorded on each.


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