Welcome to the public home of Dependabot. This repository serves 2 purposes:
- It houses the source code for Dependabot Core, which is the heart of Dependabot. Dependabot Core handles the logic for updating dependencies on GitHub (including GitHub Enterprise), GitLab, and Azure DevOps. If you want to host your own automated dependency update bot then this repo should give you the tools you need. A reference implementation is available here.
- It is the public issue tracker for issues related to Dependabot's updating logic. For issues about Dependabot the service, please contact GitHub support. While the distinction between Dependabot Core and the service can be fuzzy, a good rule of thumb is if your issue is with the diff that Dependabot created, it belongs here and for most other things the GitHub support team is best equipped to help you.
Please file an issue. Bug reports, feature requests, and general feedback are all welcome.
Contributing to Dependabot
Currently, the Dependabot team is not accepting support for new ecosystems. We are prioritising upgrades to already supported ecosystems at this time.
Please refer to the CONTRIBUTING guidelines for more information.
Disclosing security issues
If you believe you have found a security vulnerability in Dependabot please submit the vulnerability to GitHub Security Bug Bounty so that we can resolve the issue before it is disclosed publicly.
What's in this repo?
- Logic to check for the latest version of a dependency that's resolvable given a project's other dependencies
- Logic to generate updated manifest and lockfiles for a new dependency version
- Logic to find changelogs, release notes, and commits for a dependency update
Other Dependabot resources
In addition to this library, you may be interested in:
- The dependabot-script repo, which provides a collection of scripts that use this library to update dependencies on GitHub Enterprise, GitLab or Azure DevOps
- The API docs for Dependabot's hosted instance (dependabot.com)
Cloning the repository
Clone the repository with Git using:
git clone https://github.com/dependabot/dependabot-core.git
On Windows this might fail with "Filename too long". To solve this, run the following commands in the cloned Git repository:
git config core.longpaths true
git reset --hard
You can read more about this in the Git for Windows wiki.
To run all of Dependabot Core, you'll need Ruby, Python, PHP, Elixir, Node, Go, Elm, and Rust installed. However, if you just wish to run it for a single language you can get away with just having that language and Ruby.
To install the helpers for each language:
cd npm_and_yarn/helpers && npm install --production && cd -
cd composer/helpers && composer install --no-dev && cd -
cd python/helpers && pyenv exec pip install -r requirements.txt && cd -
cd hex/helpers && mix deps.get && cd -
cd terraform && helpers/build "$(pwd)/helpers/install-dir/terraform" && cd -
cd go_modules && helpers/build "$(pwd)/helpers/install-dir/go_modules" && cd -
Local development & Running tests
Run the tests by running
rspec spec inside each of the packages. Style is
enforced by RuboCop. To check for style violations, simply run
each of the packages.
Running with Docker
While you can run Dependabot Core without Docker, we also provide a development Dockerfile. In most cases, you'll be better off running Dependabot in the development Docker container as it bakes in all required dependencies.
Start by building the initial Dependabot Core image, or pull it from the Docker registry.
$ docker pull dependabot/dependabot-core # OR $ docker build -f Dockerfile -t dependabot/dependabot-core . # This may take a while
Once you have the base Docker image, you can build and run the development
container using the
docker-dev-shell script. The script will automatically
build the container if it's not present and can be forced to rebuild with the
--rebuild flag. The image includes all dependencies, and the script runs the
image, mounting the local copy of Dependabot Core so changes made locally will
be reflected inside the container. This means you can continue to use your
editor of choice while running the tests inside the container.
$ bin/docker-dev-shell => building image from Dockerfile.development => running docker development shell [dependabot-core-dev] ~/dependabot-core $ [dependabot-core-dev] ~/dependabot-core $ cd go_modules && rspec spec # to run tests for a particular package
Dry run script
You can use the "dry-run" script to simulate a dependency update job, printing the diff that would be generated to the terminal. It takes two positional arguments: the package manager and the GitHub repo name (including the account):
$ bin/docker-dev-shell $ bin/dry-run.rb go_modules rsc/quote => fetching dependency files => parsing dependency files => updating 2 dependencies ...
Debugging with Visual Studio Code and Docker
There's built-in support for leveraging Visual Studio Code's ability for
debugging inside a Docker container.
After installing the recommended
Remote - Containers extension,
⇧⌘P on macOS) and select
Remote-Containers: Reopen in Container.
You can also access the dropdown by clicking on the green button in the bottom-left corner of the editor.
If the development Docker image isn't present on your machine, it will be built automatically.
Once that's finished, start the
Debug Dry Run configuration
(F5) and you'll be prompted
to select a package manager and a repository to perform a dry run on.
Feel free to place breakpoints on the code.
Clone Repository ... commands of the Remote Containers extension are currently
missing some functionality and are therefore not supported. You have to clone the
repository manually and use the
Reopen in Container or
Open Folder in Container...
Triggering the jobs that will push the new gems is done by following the steps below.
- Ensure you have the latest merged changes:
git checkout mainand
- Generate an updated
version.rb, and the rest of the needed commands:
- Edit the
CHANGELOGfile and remove any entries that aren't needed
- Run the commands that were output by running
Dependabot Core is a collection of Ruby packages (gems), which contain the logic for updating dependencies in several languages.
common package contains all general-purpose/shared functionality. For
instance, the code for creating pull requests via GitHub's API lives here, as
does most of the logic for handling Git dependencies (as most languages support
Git dependencies in one way or another). There are also base classes defined for
each of the major concerns required to implement support for a language or
There is a gem for each package manager or language that Dependabot supports. At a minimum, each of these gems will implement the following classes:
||Fetches the relevant dependency files for a project (e.g., the
||Parses a dependency file and extracts a list of dependencies for a project. See the README for more details.|
||Checks whether a given dependency is up-to-date. See the README for more details.|
||Updates a dependency file to use the latest version of a given dependency. See the README for more details.|
||Looks up metadata about a dependency, such as its GitHub URL. See the README for more details.|
||Describes the logic for comparing dependency versions. See the hex Version class for an example.|
||Describes the format of a dependency requirement (e.g.
The high-level flow looks like this:
This is a "meta" gem, that simply depends on all the others. If you want to automatically include support for all languages, you can just include this gem and you'll get all you need.
You can profile a dry-run by passing the
--profile flag when running it, or
tag an rspec test with
:profile. This will generate a
stackprof-<datetime>.dump file in the
tmp/ folder, and you can generate a
flamegraph from this by running:
stackprof --d3-flamegraph tmp/stackprof-<data or spec name>.dump > tmp/flamegraph.html.
Why is this public?
As the name suggests, Dependabot Core is the core of Dependabot (the rest of the app is pretty much just a UI and database). If we were paranoid about someone stealing our business then we'd be keeping it under lock and key.
Dependabot Core is public because we're more interested in it having an impact than we are in making a buck from it. We'd love you to use Dependabot so that we can continue to develop it, but if you want to build and host your own version then this library should make doing so a lot easier.
If you use Dependabot Core then we'd love to hear what you build!
We use the License Zero Prosperity Public License, which essentially enshrines the following:
- If you would like to use Dependabot Core in a non-commercial capacity, such as to host a bot at your workplace, then we give you full permission to do so. In fact, we'd love you to and will help and support you however we can.
- If you would like to add Dependabot's functionality to your for-profit company's offering then we DO NOT give you permission to use Dependabot Core to do so. Please contact us directly to discuss a partnership or licensing arrangement.
If you make a significant contribution to Dependabot Core then you will be asked to transfer the IP of that contribution to Dependabot Ltd so that it can be licensed in the same way as the above.
Dependabot and Dependabot Core started life as Bump and Bump Core, back when Harry and Grey were working at GoCardless. We remain grateful for the help and support of GoCardless in helping make Dependabot possible - if you need to collect recurring payments from Europe, check them out.