> 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-code/scanning.md).

# OX Code Scanning

## About OX Code Scanning

OX Security scans your development and runtime environments to identify and prioritize security issues across the software supply chain.

OX connects to your source control, CI/CD pipelines, artifact registries, cloud environments, and external security tools to collect findings and security context. Scan results enrich the OX graph, providing a unified view of issues, ownership, impact, and required actions.

OX supports multiple scan entry points to fit different development workflows. Repository and registry integrations keep OX synchronized with your development environment so that changes such as new commits, pull requests, images, and packages can be analyzed. CI/CD pipeline scanning analyzes code and artifacts as part of the build and delivery process and can enforce OX policies before software is released.

Developers can also use OX IDE integrations to identify issues during development, or use the OX CLI to run targeted scans manually or as part of automated workflows.

### Scanning options

The OX scanning engine supports multiple scanning methods, providing flexible coverage across different workflows and environments.

| Scanning option                                                                                 | Description                                                                                                           |
| ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| [Scanning Selected Repositories](/ox-code/scanning/scanning-selected-repositories.md)           | Run scans for selected repositories when you need to scan specific parts of your environment.                         |
| [Scanning Multiple Branches](/ox-code/scanning/multi-branch-support.md)                         | Scan additional branches beyond the repository's default branch.                                                      |
| [Scanning Code and Artifacts in CI/CD Pipelines](/ox-code/scanning/scanning-ci-cd-pipelines.md) | Scan source code and software artifacts as part of your CI/CD workflows and enforce security policies before release. |
| [Monorepo Scanning](/ox-code/scanning/monorepo-scanning.md)                                     | Configure scanning for repositories that contain multiple applications or projects.                                   |
| [OX IDE Integrations](/ox-code/scanning/ox-ide-integrations.md)                                 | Integrate OX with supported development environments to identify security issues as part of the developer workflow.   |
| [OX CLI](/ox-code/scanning/ox-cli-1.md)                                                         | Run OX scans from the command line for manual, scripted, or automated scanning workflows.                             |


---

# 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-code/scanning.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.