Cannot Enable or Configure Dependabot for Organization

[cancankamoro]

Select Topic Area

Question

Feature Area

Issues

Body

Hello GitHub Support,

I am unable to enable, install, or configure Dependabot for my organization, "Kamoro Maxima Integra".

The Dependabot GitHub App is not listed under our Organization Settings > GitHub Apps page, so I cannot configure its repository access.

I have tried every documented method to enable it, and all have failed:

The direct installation URL (github.com/apps/dependabot) appears to be deprecated and does not work.

Enabling all Dependabot-related features under Organization Settings > Security > Global settings has no effect.

Creating a global .github/dependabot.ymlor a local.github/dependabot.yml in a repository does not trigger the feature. The repository's "Insights > Dependabot" tab still shows "aren't configured yet".

The "Grant Dependabot access to repositories" setting in the "Global settings" page does not resolve the issue.

Our goal is to enable Dependabot Version Updates for our private repositories.

Could you please investigate and manually enable or fix the Dependabot feature provisioning? We seem to be in a broken or non-standard state where the feature is completely unavailable.

Thank you.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[AmirhosseinHonardoust]

Hi
Dependabot is no longer a separate GitHub app, so you won’t see it under organization settings → GitHub Apps. It’s now built directly into GitHub.
to enable it:
go to settings → security & analysis (at the org or repo level) and make sure dependency graph, Dependabot alerts, security updates, and version updates are turned on.
in each repo where you want version updates, add a /.github/dependabot.yml file on the default branch. that’s what actually triggers Dependabot updates.
there’s no need to install anything. once the settings are enabled and the config file is present, Dependabot will start working.

[cancankamoro]

Thanks so much. It works now.

[ashmeet07]

🛠️ Solution: Ensure Dependency Graph is Active

The most likely reason Dependabot is unavailable, even after toggling the global settings and adding a dependabot.yml file, is that the core Dependency Graph feature is not active for your organization.

Dependabot relies on the Dependency Graph to parse manifest files and identify dependencies, and it won't run if the Graph is disabled.

Step-by-Step Fix:

1. Check Dependency Graph Status (Organization Level):

   • Go to Organization Settings.
   • In the left sidebar, select Security and analysis.
   • Find the section for Dependency graph.
   • Ensure the Dependency Graph is enabled for all repositories or at least for the specific repositories you want to use Dependabot with.

2. Verify Repository Access:

   • Still in Security and analysis, ensure the setting for "Grant Dependabot access to repositories" is enabled.

3. Trigger the Scan:

   • After enabling the Dependency Graph, push a small, insignificant update (e.g., a README change) to the default branch of the target repository. This action often forces GitHub to re-scan the repository and refresh the Dependency Graph.

Important Notes:

• Dependabot is Not a GitHub App: You are correct that you will not find "Dependabot" under Organization Settings > GitHub Apps. It is no longer a separate application; it is built directly into GitHub's Security & Analysis features.
• Final Check: After completing the steps, verify under the repository's Insights tab that the Dependency graph is populated. Once the Dependency Graph is active, Dependabot Version Updates will process your .github/dependabot.yml file on its next scheduled run.
• Contact Support: If the Dependency Graph is active and Dependabot still doesn't run, your organization may be in an inconsistent state. In this scenario, you must open a GitHub Support ticket and include the organization name and an example repository for them to manually provision the feature.

[cancankamoro]

Thanks so much. It works now.

[ashmeet07]

Great !

[cancankamoro]

Thanks so much. It works now.