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

# Overview

The **Overview** tab of Code Analysis summarizes the branches in your scope: how many have a recorded assessment, how many failed their quality gate, how pull requests are doing, and which branches to review first.

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

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

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FvCvFGaPkT3IGS8gYudxE%2Fv2-code-overview.png?alt=media&amp;token=4b802642-b3a4-4a92-a4b6-9e1682517a5f" alt="Code Analysis Overview tab with filters, metric tiles and the release evidence banner"><figcaption><p>Code Analysis overview</p></figcaption></figure>

## Filters

| Filter              | Description                                                                                                           |
| ------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Organization**    | One organization, or **All authorized organizations**.                                                                |
| **Source**          | **Bitbucket**, **GitHub**, **Design Center** or **CLI**, or **All sources**.                                          |
| **Asset type**      | One asset type (for example Mule or API), or **All asset types**.                                                     |
| **Evidence status** | **All evidence**, **Failed gates**, **Passed gates**, **No gate result**, **Never scanned** or **Older than N days**. |
| **Filters** panel   | **Severity**, **Category**, **Rule** and **Security standard**: keep branches with open findings that match.          |

**All branches** at the top right opens the [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md) tab with the same scope.

## Metric tiles

Each tile opens the records it counts.

| Tile                            | Description                                                                                          |
| ------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Branches in view**            | Branches in scope, with the number of parent applications.                                           |
| **Failed gates**                | Branches whose latest recorded quality gate failed.                                                  |
| **Critical + Blocker findings** | Open Critical and Blocker finding occurrences you are authorized to see. Opens them in **Findings**. |
| **Never scanned**               | Branches with no recorded assessment yet.                                                            |
| **Assessments to refresh**      | Branches whose latest assessment is older than the configured number of days.                        |

## Release evidence

The dark banner states how many branches have a recorded assessment (**Evidence coverage**). Missing evidence cannot establish release readiness.

* **Review never scanned** lists the branches without an assessment.
* **Review failed gates** lists the branches whose gate failed.

## Charts and lists

| Section                                          | Description                                                                                                                                                                                                                                                                                                              |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Defect progression**                           | The latest recorded assessment of each application per day. Choose **Total & high severity**, **Severity breakdown**, **Defect types** or **Gates & assessment coverage**.                                                                                                                                               |
| **Security standards**                           | How many open findings map to CWE, OWASP and the other security standards. Select a bar to list its findings.                                                                                                                                                                                                            |
| **Assets by type and quality gate**              | Failed, passed and not assessed records per asset type. Select a segment to list those records.                                                                                                                                                                                                                          |
| **Top rules behind Critical + Blocker findings** | The rules with the most Critical and Blocker occurrences. Select a bar to list the applications with that rule's findings.                                                                                                                                                                                               |
| **Pull requests (30 days)**                      | **Open pull requests**, **First-time pass rate**, **Median new findings** and **Pull requests assessed**. See [Pull Requests](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/pull-requests.md).                                                                      |
| **Branches to review first**                     | Branches with the most high-severity occurrences, then a failed gate, then the most recorded findings: **Branch**, **Gate evidence**, **Critical / Blocker**, **Last assessment** and **Review** (opens the dossier). **View all** opens the full list. Columns chooses the columns shown and Export downloads the list. |

Every chart has **Show data table**.

## Next Steps

* [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md): open a branch's dossier.
* [Pull Requests](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/pull-requests.md): review the gate of each pull request.
* [Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/findings.md): investigate the findings behind a failed gate.
* [Code Analysis](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis.md): back to the workspace.


---

# 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/overview.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.
