> 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/semgrep.md).
# Semgrep
Import Semgrep Supply Chain (SCA) and Semgrep Code (SAST) findings into Konvu for exploitability analysis.
The Semgrep integration imports findings from Semgrep Supply Chain (SCA) and Semgrep Code (SAST) into Konvu. Konvu does not process findings from Semgrep Secrets.
## What this integration brings in
* Vulnerability identifiers (CVE/GHSA) and severity ratings from Semgrep Supply Chain
* Affected dependency name, version, and ecosystem
* Lockfile locations linking findings to specific manifests
* Finding state (open, fixed, ignored)
{% hint style="info" %}
The Semgrep integration is configured at the organization level. You can connect as many Semgrep organizations as needed.
{% endhint %}
## Prerequisites
* A Semgrep account with at least one organization using Semgrep Supply Chain
* A Semgrep API token with **Web API** scope ([create one here](https://semgrep.dev/orgs/-/settings/tokens))
## Setup steps
1. Go to your [Semgrep organization token settings](https://semgrep.dev/orgs/-/settings/tokens).
2. Create a new token with the **Web API** scope and copy it.
Create a Semgrep token with Web API scope
3. Navigate to [**Integrations**](https://app.konvu.com/integrations) in Konvu and select **Semgrep**.
4. Paste your Semgrep token and click **Submit**.
Add your Semgrep token and click submit
{% hint style="info" %}
You can repeat these steps to connect additional Semgrep organizations.
{% endhint %}
## Verify findings are flowing
After connecting, Konvu runs an initial sync. To confirm it worked:
1. Go to **Integrations** in Konvu and check that the Semgrep integration shows a successful sync status.
2. Click the integration to see imported repositories and finding counts.
3. Navigate to the **Triage** page -- your Semgrep Supply Chain findings should appear there.
If the sync shows an error, verify that your token has the **Web API** scope and that the organization has Semgrep Supply Chain projects.
## 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 Semgrep 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/semgrep.md?ask=&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.
