> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/finding-types.md).

# Finding Types

What Konvu does for each kind of finding, from assessment to reproduction and fixes.

Konvu handles five kinds of findings. Each follows the same path: bring it in, triage it, fix it. What Konvu checks, and what it can do after triage, depends on the type. Each page below covers one type end to end.

|                                                                                                   | Assessed                     | Reproduced                | Fix pull requests      | Write-back to source                                 |
| ------------------------------------------------------------------------------------------------- | ---------------------------- | ------------------------- | ---------------------- | ---------------------------------------------------- |
| [**Dependencies (SCA)**](/konvu/triage-and-remediation/finding-types/dependencies.md)             | Yes                          | Early access              | Yes                    | Dismissals, assessments (ArmorCode)                  |
| [**Code (SAST)**](/konvu/triage-and-remediation/finding-types/code.md)                            | Yes                          | Early access, CodeQL only | Yes                    | Dismissals (CodeQL, GitLab), assessments (ArmorCode) |
| [**Containers**](/konvu/triage-and-remediation/finding-types/containers.md) (beta)                | Yes                          | No                        | No                     | Assessment notes (Wiz)                               |
| [**Secrets**](/konvu/triage-and-remediation/finding-types/secrets.md)                             | Validity, impact, exposure   | No                        | No                     | No                                                   |
| [**Vulnerability Reports**](/konvu/triage-and-remediation/finding-types/vulnerability-reports.md) | Triage against program rules | Yes                       | No, fix prompt instead | No                                                   |

## What each type checks

* **Dependencies**: whether the conditions for exploiting the vulnerability hold in your code: installed version, environment, reachability, and attacker-controlled input.
* **Code**: where the flagged input comes from, whether an attacker controls it, and what stands between it and the flagged code.
* **Containers**: whether the operating-system conditions for the vulnerability hold in the image.
* **Secrets**: whether the credential works, what it grants access to, and how an attacker could obtain it.
* **Vulnerability reports**: whether the report is in scope, whether it duplicates another report, and whether the exploit fires against your application.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konvu.com/konvu/triage-and-remediation/finding-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.