Examples of how you can use GitHub Actions to automate common Dependabot related tasks.| GitHub Docs
GitHub automatically runs the jobs that generate Dependabot pull requests on GitHub Actions if you have GitHub Actions enabled for the repository. When Dependabot is enabled, these jobs will run by bypassing Actions policy checks and disablement at the repository or organization level.| GitHub Docs
You can use Dependabot security updates or manual pull requests to easily update vulnerable dependencies.| GitHub Docs
You can use Dependabot to keep the packages you use updated to the latest versions.| GitHub Docs
You can use the dependency submission API to submit dependencies for projects, such as the dependencies resolved when a project is built or compiled.| GitHub Docs
You can use the dependency graph to see the packages your project depends on and the repositories that depend on it. In addition, you can see any vulnerabilities detected in its dependencies.| GitHub Docs
Dependency review lets you catch insecure dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.| GitHub Docs
Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates.| GitHub Docs
GitHub sends Dependabot alerts when we detect that your repository uses a vulnerable dependency.| GitHub Docs
You can configure your repository so that Dependabot automatically updates the packages you use.| GitHub Docs
You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems.| GitHub Docs
GitHub makes extra security features available to customers who purchase GitHub Code Security or GitHub Secret Protection. Some features are enabled for public repositories by default.| GitHub Docs