Explore the dependency graph

Read the graph#

Open Dependency graph. Each top-level node represents a selected GitHub repository. Arrows go from the caller repository toward the provider repository, with counts of distinct directed module dependencies.

Select a repository to open its module graph. Neighboring repositories stay collapsed, and incoming and outgoing dependencies remain visible. Select a module to inspect its APIs or an arrow to inspect the underlying API relationships and source evidence. Use the Repositories breadcrumb to return to the overview.

Inspect relationships#

1. 1

   Find a repository or module

   Search by repository name, module name, or path. The evidence filter offers static, runtime, or combined evidence. Static and Runtime each include relationships supported by both evidence sources.

2. 2

   Open a repository

   Select a repository card or inventory entry. The module graph uses automatic layout. Large repositories offer Connected and All modules views; every module remains available in the inventory.

3. 3

   Inspect a module

   Select a module to see its path and defined APIs. Module selection preserves the graph layout and zoom. Select an API link to open its details and code flow.

4. 4

   Inspect a dependency

   Select an arrow to see the caller and provider modules, API relationships, evidence type, confidence, and source references. Repository edge counts represent module dependencies; API counts represent distinct caller module and endpoint pairs.

5. 5

   Reset the view

   Choose Fit view to bring graph nodes into view. Use Clear to reset search and evidence filters.

Export a snapshot#

Choose Export snapshot to download impact-gate-dependencies.json. The export includes the snapshot identity, repository scope, repositories, modules, aggregate dependencies, count definitions, services, endpoints, and underlying edges. It exports the full scoped snapshot even when the graph view is filtered.

Use the snapshot ID and source commit references when sharing a dependency review. The export can contain private repository paths and source links; share it according to your organization's access rules.