> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-integrations/3rd-party-integrations/source-control.md).

# Source Control

Source Control connectors connect OX to version control platforms that host and manage source code repositories, branches, and collaboration workflows.

OX imports data from these tools through APIs, enriches it with OX context (application mapping, ownership, workflows, and compliance), and presents it alongside findings from other scanners and tools in a unified view.

## What OX adds

* **Context and correlation:** OX maps findings to applications, services, and teams to show impact and ownership.
* **Prioritization with severity factors:** OX may reprioritize scanner severities when exploitability and environment context reduce risk (for example, Critical → High). Severity factors explain why the priority changed.
* **Evidence at a glance:** When available, OX displays scanner evidence, file locations, and remediation guidance alongside OX analytics to speed triage.

## Where data appears

* **Active Issues:** Filter by **Source tool** to focus on findings from a specific connector.
* **Issue details:** Tabs show scanner evidence, asset data, and OX correlations such as application and repository mapping.
* **Assets and applications:** Imported assets appear in asset views, application context, and dashboards.
* **Risk prioritization:** Findings are ranked using combined development, pipeline, and runtime signals.

## Supported connectors

See the articles in **Get Started > Onboarding to OX >** [Connect Source Control](/get-started/onboarding-to-ox/source-control.md).

* [AWS CodeCommit](/ox-integrations/3rd-party-integrations/cloud-security/aws-1.md)
* [Azure Repos](/get-started/onboarding-to-ox/source-control/azure.md)
* Azure TFS
* [BitBucket Cloud](/get-started/onboarding-to-ox/source-control/bitbucket.md)
* Bitbucket Data Center/Server
* [Gerrit Code Review](/get-started/onboarding-to-ox/source-control/gerrit-code-review.md)
* [GitHub](/get-started/onboarding-to-ox/source-control/github.md)
* [GitLab](/get-started/onboarding-to-ox/source-control/gitlab.md)


---

# 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.ox.security/ox-integrations/3rd-party-integrations/source-control.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.