> 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/connect-your-environment/source-code.md).

# Source Code

Connect your SCM so Konvu can analyze whether vulnerable dependencies are reachable in your code.

Konvu analyzes your codebase to determine whether vulnerable dependencies are actually reachable. It identifies your technology stack -- programming languages, frameworks, operating systems, package managers, and frontend vs. backend boundaries -- then cross-references this against exploit conditions from your SCA findings. If a vulnerability requires a runtime or framework you don't use, Konvu flags it as not applicable.

## Deployment options

### Managed Analysis

Konvu hosts the analysis infrastructure. You connect your SCM through a GitHub App or GitLab integration, and Konvu clones repositories into ephemeral environments for analysis. Code is never stored.

**Use this when:** You want the fastest setup and don't need to keep code access within your own infrastructure.

* [GitHub Installation](/konvu/get-started/connect-your-environment/source-code/managed-analysis/github-installation.md)
* [GitLab Installation](/konvu/get-started/connect-your-environment/source-code/managed-analysis/gitlab-installation.md)

### Self-Hosted Analysis

You deploy Konvu's broker and controller in your own Kubernetes cluster. Code never leaves your infrastructure.

**Use this when:** Your security policy requires that source code stays within your network, or you need to analyze repositories on private GitHub Enterprise Server instances without external access.

* [Self-Hosted Analysis guide](/konvu/get-started/connect-your-environment/source-code/self-hosted-analysis.md)

## Comparison

|                              | Managed Analysis                      | Self-Hosted Analysis      |
| ---------------------------- | ------------------------------------- | ------------------------- |
| **Setup time**               | Minutes                               | 15--30 minutes            |
| **Infrastructure**           | Konvu-managed                         | Your Kubernetes cluster   |
| **Code leaves your network** | Temporarily, in ephemeral environment | Never                     |
| **SCM support**              | GitHub (Cloud + GHES), GitLab         | GitHub (Cloud + GHES)     |
| **Maintenance**              | None                                  | You manage the deployment |


---

# 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/connect-your-environment/source-code.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.