> 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/get-started/bring-in-findings/code-scanners/arnica.md).

# Arnica

Import Arnica SCA findings into Konvu for exploitability analysis.

The Arnica integration imports SCA vulnerability findings from Arnica into Konvu. Arnica provides package-level context including reachability status and package type, which Konvu uses to inform exploitability assessments.

## What this integration brings in

* Vulnerability identifiers (CVE IDs) from Arnica findings
* Affected dependency name, version, and ecosystem (npm, pip, Maven, RubyGems, Go, Cargo, NuGet, Composer)
* Manifest file locations from repository asset data
* Reachability status when available from Arnica
* Direct vs. transitive dependency classification
* Finding state (open, dismissed, resolved)
* Dismissal reasons for previously triaged findings

{% hint style="info" %}
The Arnica integration is configured at the organization level. Each integration maps to one Arnica organization.
{% endhint %}

## Prerequisites

* An Arnica account with API access
* An API key from Arnica (found in your Arnica settings)

## Setup steps

1. In the Arnica console, go to your account settings and generate an API key. Copy it.
2. Navigate to [**Integrations**](https://app.konvu.com/integrations) in Konvu.
3. Click **Arnica**.
4. Enter the following:
   * **API Key** -- your Arnica API key
   * **Namespace** -- a display name for this integration (e.g., your organization name)
5. Click **Submit**. Konvu validates your API key before creating the integration.

If validation fails, you will see an error indicating invalid credentials. Verify your API key is correct and has not expired.

## Verify findings are flowing

After connecting, Konvu runs an initial sync to import your SCA findings. To confirm:

1. Go to **Integrations** in Konvu and check that the Arnica integration shows a successful sync status.
2. Click the integration to see the list of imported repositories and their finding counts.
3. Navigate to the **Triage** page -- your Arnica findings should appear there.

If the sync shows an error, verify that:

* Your API key is still valid
* The Arnica organization has repositories with SCA findings
* The API key has permission to read findings and repositories

## Next steps

* [Connect your environment](/konvu/get-started/connect-your-environment.md) to give Konvu source code context for exploitability analysis
* [Triage findings](/konvu/triage-and-remediation/exploitability-assessment.md) to review Konvu's AI-driven assessments on your Arnica findings


---

# 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/get-started/bring-in-findings/code-scanners/arnica.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.