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

# Branch Dependencies

The **Branch dependencies** tab of Code Analysis shows the dependencies recorded for your applications: the components, services and endpoints they reference, and which applications consume each one. Use it before changing a shared component to see what the change could reach.

Open it from **Workspaces** → **Code Analysis** → **Branch dependencies** 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%2FqxsBYrhN4O9C6JbbYwWD%2Fv2-code-deps.png?alt=media&amp;token=8e55f20a-b372-44d0-b901-5790f6ea3c2a" alt="Branch dependencies tab with view switch, metric tiles and the dependency explorer"><figcaption><p>Branch dependencies</p></figcaption></figure>

## Scope and views

Choose the **Organization** (or **All authorized organizations**) and the **Source** (or **All sources**) at the top. Then pick a view:

| View                      | Description                                                                                                                                                |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Focused explorer**      | One application or reference at a time, with its direct dependencies or consumers.                                                                         |
| **End-to-end graph**      | The recorded dependencies and consumers of the focused application across several hops. Available once an application or reference is in focus.            |
| **All relationship rows** | **Every recorded relationship**, including upstream and containment rows: **Source application**, **Direction**, **Reference**, **Kind** and **Navigate**. |

## Metric tiles

| Tile                      | Description                                                                                 |
| ------------------------- | ------------------------------------------------------------------------------------------- |
| **Referenced components** | Direct downstream and endpoint references in scope.                                         |
| **Shared dependencies**   | References with more than one recorded consumer.                                            |
| **Recorded consumers**    | Applications that consume these references.                                                 |
| **Direct observations**   | All relationship rows, including upstream and containment. Opens **All relationship rows**. |

## Explore an application's dependencies

1. In **Dependency explorer**, choose **With dependencies** or **All applications** in the list on the left, or **Referenced components** to start from a component.
2. Click an application. It becomes the focus of the graph.
3. To narrow the references, type in **Find a secret, service, or dependency…** or choose **Multiple consumers** instead of **All references**.
4. Select a reference to see the applications that consume it.
5. Use **Explore dependencies** on a consumer to make it the focus, or **Open dossier** to open its dossier.
6. Click **Inspect N consumers** to list every consumer, or **Prepare change review** to prepare a review of a change to that reference.

The breadcrumb above the graph (**All dependencies** / application / reference) takes you back a level. **Open application dossier** opens the focused application. The link icon copies a link to the focused dependency, and **Reset reference filters** clears the search and filters.

{% hint style="info" %}
Connections show the direct references the source reported. They do not prove transitive reach, runtime traffic or business impact, and a missing relationship is a gap in the evidence, not proof of isolation. Links that a person declared in the dossier (**Link applications**) are shown as declared, and scans never change them.
{% endhint %}

## Next Steps

* [Dependency Insights](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights.md): plan versions, risks and actions across connected applications.
* [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md): open a repository's dossier.
* [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/branch-dependencies.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.
