> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis.md).

# Code Analysis

Code Analysis shows the source quality of your repositories: the quality gate and findings of each branch and pull request, the baseline each repository is measured against, and which repositories are scanned. Use it to decide whether a branch is ready to release and what to fix first.

Open it from **Workspaces** → **Code Analysis** in the sidebar.

{% hint style="info" %}
Requires the **Code Analysis** licence.
{% endhint %}

{% hint style="warning" %}
You need a role that can view Code Analysis applications. The workspace shows only the organizations and sources your role covers.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FARmlbx5uc4zo9EQxFImx%2Fcode-workspace-z18.png?alt=media&amp;token=d834aa7b-c108-45cb-b652-8272d825c0df" alt="Code Analysis workspace with its six tabs"><figcaption><p>Code Analysis workspace</p></figcaption></figure>

## Tabs

| Tab                                                                                                                                                  | Use it to                                                                                  |
| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| [Overview](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/overview.md)                           | See gate results, evidence coverage, pull request health and the branches to review first. |
| [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md) | List repositories and their branches, open a branch's dossier and manage it.               |
| [Pull Requests](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/pull-requests.md)                 | Review the gate and new findings of each pull request.                                     |
| [Branch Dependencies](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branch-dependencies.md)     | Explore the recorded dependencies between your applications.                               |
| [Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/findings.md)                           | Investigate open findings, estimate the time to fix them and review exceptions.            |
| [Manage Scanning](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/manage-scanning.md)             | Choose which Bitbucket, GitHub and Design Center repositories and projects are scanned.    |

## Where the branches come from

Branches and pull requests reach Code Analysis from:

* **Bitbucket** and **GitHub** repositories that IZ Suite discovers and scans on a schedule ([Manage Scanning](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/manage-scanning.md)).
* **Design Center** projects, scanned on a schedule.
* Your CI/CD pipeline or a command line, through the CLI (**CLI / upload** in the lists). See [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md).

## Header actions

| Action        | Description                                        |
| ------------- | -------------------------------------------------- |
| **Copy link** | Copies the address of the current tab and filters. |

The filters, saved filters and table tools work as described in [Workspaces](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces.md). AI reviews are requested for one application at a time, from its dossier: see [AI Focus Report](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/ai-focus-report.md).

## Next Steps

* [Overview](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/overview.md): see which branches need a review.
* [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md): open a branch's dossier.
* [Manage Scanning](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/manage-scanning.md): choose the repositories to scan.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis.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.
