About Dependabot for GitHub Enterprise Server
Dependabot helps users of GitHub Enterprise Serverインスタンス find and fix vulnerabilities in their dependencies. You can enable Dependabotアラート to notify users about vulnerable dependencies and Dependabot updates to fix the vulnerabilities and keep dependencies updated to the latest version.
Dependabotアラートについて
With Dependabotアラート, GitHub identifies insecure dependencies in repositories and creates alerts on GitHub Enterprise Serverインスタンス, using data from the GitHub Advisory Database and the dependency graph service.
We add advisories to the GitHub Advisory Database from the following sources:
- National Vulnerability Database
- GitHub上のパブリックなコミット内の脆弱性の検出に、機械学習と人間によるレビューの組み合わせ
- GitHubで報告されたセキュリティアドバイザリ
- npm Security advisoriesデータベース
After you enable Dependabotアラート for your enterprise, vulnerability data is synced from the GitHub Advisory Database to your instance once every hour. Only GitHub-reviewed advisories are synchronized. 詳しい情報については、「GitHub Advisory Database のセキュリティアドバイザリを参照する」を参照してください。
また、脆弱性データはいつでも手動で同期することができます。 For more information, see "Viewing the vulnerability data for your enterprise."
Note: When you enable Dependabotアラート, no code or information about code from GitHub Enterprise Serverインスタンス is uploaded to GitHub.com.
When GitHub Enterprise Serverインスタンス receives information about a vulnerability, it identifies repositories in GitHub Enterprise Serverインスタンス that use the affected version of the dependency and generates Dependabotアラート. You can choose whether or not to notify users automatically about new Dependabotアラート.
For repositories with Dependabotアラート enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to GitHub Enterprise Serverインスタンス, GitHub Enterprise Server scans all existing repositories on GitHub Enterprise Serverインスタンス and generates alerts for any repository that is vulnerable. 詳しい情報については、「Dependabotアラート について」を参照してください。
Dependabot updatesについて
After you enable Dependabotアラート, you can choose to enable Dependabot updates. When Dependabot updates are enabled for GitHub Enterprise Serverインスタンス, users can configure repositories so that their dependencies are updated and kept secure automatically.
Note: Dependabot updates on GitHub Enterprise Server requires GitHub Actions with self-hosted runners.
By default, GitHub Actions runners used by Dependabot need access to the internet, to download updated packages from upstream package managers. For Dependabot updates powered by GitHub Connect, internet access provides your runners with a token that allows access to dependencies and advisories hosted on GitHub.com.
With Dependabot updates, GitHub automatically creates pull requests to update dependencies in two ways.
- Dependabotバージョンアップデート: Users add a Dependabot configuration file to the repository to enable Dependabot to create pull requests when a new version of a tracked dependency is released. 詳しい情報については「Dependabotバージョンアップデートについて」を参照してください。
- Dependabotセキュリティアップデート: Users toggle a repository setting to enable Dependabot to create pull requests when GitHub detects a vulnerability in one of the dependencies of the dependency graph for the repository. For more information, see "About Dependabotアラート" and "About Dependabotセキュリティアップデート."
Dependabotアラート の有効化
Before you can enable Dependabotアラート:
- You must enable GitHub Connect. For more information, see "Managing GitHub Connect."
- You must enable the dependency graph. For more information, see "Enabling the dependency graph for your enterprise."
-
GitHub Enterprise Serverの右上で、プロフィール写真をクリックし、続いてEnterprise settings(Enterpriseの設定)をクリックしてください。
-
In the enterprise account sidebar, click GitHub Connect.
-
Under "Dependabot", to the right of "Users can receive vulnerability alerts for open source code dependencies", select the dropdown menu and click Enabled without notifications. Optionally, to enable alerts with notifications, click Enabled with notifications.
Tip: We recommend configuring Dependabotアラート without notifications for the first few days to avoid an overload of emails. 数日後、通知を有効化すれば、通常どおり Dependabotアラート を受信できます。
Dependabot updates の有効化
After you enable Dependabotアラート for your enterprise, you can enable Dependabot updates.
Before you enable Dependabot updates, you must configure GitHub Enterprise Serverインスタンス to use GitHub Actions with self-hosted runners. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."
Dependabot updates are not supported on GitHub Enterprise Server if your enterprise uses clustering.
-
http(s)://HOSTNAME/login
でGitHub Enterprise Serverインスタンスにサインインしてください。 -
From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .
-
If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.
-
左のサイドバーでManagement Consoleをクリックしてください。
-
左のサイドバーでSecurity(セキュリティ)をクリックしてください。
-
Under "Security", select Dependabotセキュリティアップデート.
-
左のサイドバーの下でSave settings(設定の保存)をクリックしてください。
Note: Saving settings in the Management Console restarts system services, which could result in user-visible downtime.
-
設定が完了するのを待ってください。
-
Visit your instance(インスタンスへのアクセス)をクリックしてください。
-
Configure self-hosted runners to create the pull requests that will update dependencies. For more information, see "Managing self-hosted runners for Dependabot updates on your enterprise."
-
GitHub Enterprise Serverの右上で、プロフィール写真をクリックし、続いてEnterprise settings(Enterpriseの設定)をクリックしてください。
-
In the enterprise account sidebar, click GitHub Connect.
-
Under "Dependabot", to the right of "Users can easily upgrade to non-vulnerable open source code dependencies", click Enable.
When you enable Dependabotアラート, you should consider also setting up GitHub Actions for Dependabotセキュリティアップデート. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "Managing self-hosted runners for Dependabot updates on your enterprise."
If you need enhanced security, we recommend configuring Dependabot to use private registries. For more information, see "Managing encrypted secrets for Dependabot."