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

# Dependency Insights

Dependency Insights shows the dependencies, component versions and lifecycle or vulnerability matches recorded for your applications. Use it to see what a change could reach before you make it, and to plan and track upgrades across many applications.

Open it from **Workspaces** → **Dependency Insights** in the sidebar.

{% hint style="info" %}
Requires the **Dependency Insights** licence.
{% endhint %}

{% hint style="warning" %}
You need a role that can view the inventory. Some tabs inside a view need more: for example **Vulnerability catalog** needs access to vulnerable applications and **Deprecation rules** needs access to deprecations.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FmYyq1c4RdhnyfMK5fsLG%2Fv2-di-workspace.png?alt=media&amp;token=a906a7bb-0dd5-47a8-bda6-969db233f189" alt="Dependency Insights workspace with its view tabs"><figcaption><p>Dependency Insights</p></figcaption></figure>

## Views

Every view has the same tabs across the top and the same scope bar: **Organization**, **Platform** and **Asset type**. You can save a scope with **Save filters** and pick it again from **Saved filters**. The scope you choose stays the same when you switch views.

| View                                                                                                                                                         | What it is for                                                                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
| [Exposure](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/exposure.md)                             | Summary of shared dependencies, advisory and lifecycle matches, and where to start.                                                           |
| [Asset Exposure](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/asset-exposure.md)                 | One row per application version with its connections, components and active risk.                                                             |
| [Dependency Explorer](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/dependency-explorer.md)       | Trace recorded relationships between applications, components and endpoints.                                                                  |
| [Version Planning](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/version-planning.md)             | Component versions in use, exact inventory and upgrade waves.                                                                                 |
| [Risk & Lifecycle](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/risk-and-lifecycle.md)           | Application risk, the vulnerability catalog, deprecation rules and the priority matrix.                                                       |
| [Actions](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/updates-and-maintenance/actions.md)       | Assigned upgrade waves and saved risk review notes. A tab of **Updates & maintenance**; **Open actions queue** on **Exposure** also opens it. |
| [Updates & Maintenance](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/updates-and-maintenance.md) | Rules that tell affected teams about a change or assign maintenance work.                                                                     |
| [Assigned Work](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/assigned-work.md)                                                  | The shared queue of upgrades, maintenance, change reviews and acknowledgments.                                                                |

{% hint style="info" %}
Counts describe the evidence that has been collected. A missing record does not mean an application is safe or isolated.
{% endhint %}

## Next Steps

* [Exposure](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/exposure.md): start with the summary of shared dependencies and risk.
* [Version Planning](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/version-planning.md): plan an upgrade wave for a component.
* [Risk & Lifecycle](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/risk-and-lifecycle.md): review vulnerability and deprecation matches.


---

# 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/dependency-insights.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.
