Software often relies on packages from various sources, creating dependency relationships that can unknowingly introduce security vulnerabilities. When your code depends on packages with known security vulnerabilities, you become a target for attackers seeking to exploit your system—potentially gaining access to your code, data, customers, or contributors. Dependabot alerts notify you about vulnerable dependencies so you can upgrade to secure versions and protect your project.
When Dependabot sends alerts
Dependabot scans your repository's default branch and sends alerts when:
- New advisory data is synchronized to GitHub each hour from GitHub.com. Weitere Informationen finden Sie unter Durchsuchen von Sicherheitsempfehlungen in der GitHub Advisory Database.
- Your dependency graph changes—for example, when you push commits that update packages or versions
For supported ecosystems, see Von Abhängigkeitsdiagrammen unterstützte Paket-Ökosysteme.
Understanding alerts
When GitHub detects a vulnerable dependency, a Dependabot alert appears on the repository's Security tab and dependency graph. Each alert includes:
- A link to the affected file
- Details about the vulnerability and its severity
- Information about a fixed version (when available)
For information about viewing and managing alerts, see Anzeigen und Aktualisieren von Dependabot-Warnungen.
Who can enable alerts?
Repository administrators and organization owners can enable Dependabot alerts for their repositories. When enabled, GitHub immediately generates the dependency graph and creates alerts for any vulnerable dependencies it identifies.
Unternehmensbesitzer müssen Dependabot alerts für Ihre GitHub Enterprise Server-Instance aktivieren, bevor du dieses Feature nutzen kannst. Weitere Informationen finden Sie unter Aktivieren von Dependabot für dein Unternehmen.
See Konfigurieren von Dependabot-Warnungen.
How alert notifications work
By default, GitHub sends email notifications about new alerts to people who both:
- Have write, maintain, or admin permissions to a repository
- Are watching the repository and have enabled notifications for security alerts or for all activity on the repository
Regardless of your notification preferences, when Dependabot is first enabled, GitHub does not send notifications for all vulnerable dependencies found in your repository. Instead, you will receive notifications for new vulnerable dependencies identified after Dependabot is enabled, if your notification preferences allow it.
If you are concerned about receiving too many notifications, we recommend leveraging Dependabot auto-triage rules to auto-dismiss low-risk alerts. Rules are applied before alert notifications are sent, so alerts that are auto-dismissed upon creation do not send notifications. See Automatische Triageregeln von Dependabot.
Alternatively, you can opt into the weekly email digest, or even completely turn off notifications while keeping Dependabot alerts enabled.
Limitations
Dependabot alerts have some limitations:
- Alerts can't catch every security issue. Always review your dependencies and keep manifest and lock files up to date for accurate detection.
- New vulnerabilities may take time to appear in the GitHub Advisory Database and trigger alerts.
- Only advisories reviewed by GitHub trigger alerts.
- Dependabot doesn't scan archived repositories.
- Dependabot doesn't generate alerts for malware.
- Bei GitHub Actions werden Warnungen nur für Aktionen generiert, die die semantische Versionierung verwenden, nicht für SHA-Versionierung.