# Enable the GitHub Dependency Graph for SBOM Insights

By enabling the Dependency Graph and generating your SBOM, you’ll unlock critical insights about your project's dependencies. This information integrates seamlessly with our platform to provide enhanced analysis, detect vulnerabilities, and improve your software's security posture.

<figure><img src="/files/uvjyBAeIeTNq3hf9MBnj" alt=""><figcaption></figcaption></figure>

#### **How to Enable the Dependency Graph for Your GitHub Repository**

Follow these simple steps to enable the **Dependency Graph** in your GitHub repository:

1. **Navigate to Your Repository**\
   Go to the main page of your GitHub repository.
2. **Access the Insights Tab**
   * At the top of your repository page, click on the **Insights** tab (represented by a graph icon in the navigation bar).
3. **Open the Dependency Graph**
   * In the left sidebar, find and click on **Dependency graph**.
4. **Enable the Dependency Graph**
   * On the **Dependency graph** page, you will see a message stating that the dependency graph is not enabled.
   * Click the green **Enable the dependency graph** button to activate the feature.
5. **Confirm Activation**
   * Once enabled, the Dependency Graph will track your repository's dependencies and sub-dependencies.

By completing these steps, you'll unlock the ability to generate and download a Software Bill of Materials (SBOM) and improve your project's dependency visibility.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.codefortify.ai/getting-started/enable-the-github-dependency-graph-for-sbom-insights.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.