Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Dependabot is GitHub’s built-in dependency updater. It raises alerts for vulnerable packages, opens pull requests that patch them, and keeps ordinary dependencies current on a schedule.

What Is Dependabot?
Dependabot is the dependency updater built into GitHub. It does three separate jobs that are easy to confuse: it raises alerts when a dependency in your manifest matches an entry in the GitHub Advisory Database, it opens security updates as pull requests that bump the affected package to a fixed version, and it opens version updates on a schedule to keep dependencies current regardless of whether a vulnerability exists.
It began as an independent service built by Grey Baker and Harry Marr, which GitHub acquired in May 2019 and folded into the platform at no cost for public and private repositories alike.
Alerts need only to be switched on. Version updates require .github/dependabot.yml:
version: 2
updates:
- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
day: "monday"
open-pull-requests-limit: 5
groups:
dev-dependencies:
dependency-type: "development"
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"
Supported ecosystems include npm and Yarn, pip and Poetry, Bundler, Maven, Gradle, NuGet, Go modules, Composer, Cargo, Docker, Terraform, and GitHub Actions. That last entry is the one teams most often forget and the one that matters most right now, because a compromised third-party action runs with access to your workflow’s secrets.
The original failure mode was volume. A monorepo with four ecosystems could produce thirty open pull requests in a week, each requiring a review and a continuous integration run, and the predictable result was that developers stopped reading them. Teams disabled the feature and told themselves they would patch manually.
Grouped updates, which became generally available in 2023, let you collapse related bumps into a single pull request by ecosystem, dependency type, or name pattern. One pull request per week containing every patch-level update, with one CI run and one review, is a workload a team will sustain. Combine grouping with open-pull-requests-limit and a weekly rather than daily schedule, and the backlog stays readable.
An alert means a vulnerable version is present in a lock file. It does not mean the vulnerable function is called, reachable from untrusted input, or exploitable in your deployment. A development-only test runner with a prototype pollution advisory and an internet-facing parser with a deserialisation flaw both arrive as the same red badge. Treating them identically wastes the capacity you need for the second one.
Dependabot offers limited triage: alerts can be dismissed with a reason, and the advisory shows severity and affected version ranges. Deeper reachability analysis belongs to tools such as Snyk or a software bill of materials paired with VEX statements. What Dependabot does well is make sure nothing sits unnoticed, which is the harder half of vulnerability management in practice.
Dependabot pull requests run with a restricted token and do not expose repository secrets to workflows triggered by them, a change made after researchers showed that a malicious dependency update could otherwise exfiltrate credentials through a pull_request_target workflow. Keep it that way: do not add workarounds that hand full secrets to automated update branches.
Automerging deserves the same caution. Merging patch-level updates automatically once tests pass is reasonable for a well-tested service; doing it for a package that executes install scripts is how a supply chain attack reaches production without a human in the loop. A short cooling-off period before accepting a brand-new release is a cheap and effective safeguard.
Both solve the same problem. Dependabot is already present on GitHub, needs almost no setup, and is the pragmatic default. Renovate supports far more platforms and package managers, offers much finer control over scheduling, grouping, and automerge rules, and can pin GitHub Actions to immutable commit digests. Teams usually start with Dependabot and move when its configuration runs out of expressiveness.
For UK organisations, keeping dependencies patched is not only good practice. Cyber Essentials requires that vulnerabilities rated high or critical be fixed within 14 days of a patch becoming available, and an automated updater with a short review cycle is the simplest way to evidence that for software dependencies.
Yes. Alerts, security updates, and version updates are available at no cost on public and private repositories on GitHub.com, and on GitHub Enterprise Server once an administrator enables the dependency graph and configures a runner for Dependabot jobs. There is no separate licence, although some related features such as dependency review in pull requests on private repositories require GitHub Advanced Security.
Use grouped updates to collapse related bumps into one pull request, set a weekly rather than daily schedule, and cap the open pull request limit per ecosystem. You can also restrict version updates to security-relevant ecosystems and ignore specific packages or major version jumps. Reducing noise matters more than coverage, because an ignored queue protects nothing.
For patch and minor updates in a repository with meaningful test coverage, automerging is reasonable and keeps the queue short. Be more careful with packages that run install scripts, with major version changes, and with brand-new releases, where a short delay before accepting gives the ecosystem time to spot a malicious publish. Never automerge updates to anything that handles authentication without a review.
Not really. It is a GitHub feature and is tightly coupled to the platform, the Advisory Database, and the pull request model. If your code lives on GitLab, Bitbucket, Azure DevOps, or a self-hosted Gitea instance, Renovate is the usual choice because it runs as a self-hostable bot that supports all of those platforms and a far wider range of package managers.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.