# Install dependabot with Homebrew Tool for testing and debugging Dependabot update jobs. Version 1.91.0 via Homebrew; verified 2026-07-28. ## Install ```sh sudo av install brew:dependabot ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install dependabot ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:dependabot - **Package manager:** Homebrew - **Version:** 1.91.0 - **Source summary:** Tool for testing and debugging Dependabot update jobs - **Homepage:** - **Repository:** - **Last updated:** 2026-07-28T14:10:38+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - dependabot (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 1.91.0 ## Project history and usage Dependabot CLI is the command-line companion for running Dependabot update jobs outside the hosted GitHub workflow. It is aimed less at end users casually enabling dependency updates and more at maintainers, security engineers, and package ecosystem developers who need to reproduce, debug, or smoke-test the exact update jobs that Dependabot runs. ### Project history The CLI repository was created under the official Dependabot GitHub organization in 2022. Its README describes a Go command that runs Dependabot jobs, pulls the updater and proxy container images, and records the pull-request operations that a hosted Dependabot run would normally perform. The tool is closely tied to Dependabot's broader configuration model: the same package ecosystem names, repository paths, registry credentials, and update-job concepts show up in both CLI job files and GitHub's official dependabot.yml documentation. ### Adoption history Adoption is mainly among people who already operate Dependabot at scale. The README points users to Go installation, GitHub releases, and Homebrew, which made the tool easy to reach from developer laptops and CI debugging sessions without building Dependabot internals by hand. ### How it is used Typical usage is to run `dependabot update` for a package ecosystem and repository, or to pass a YAML job description for security-update and private-registry cases. The CLI can pass tokens from environment variables into the proxy so that the updater can access GitHub APIs and package registries without directly receiving secrets. ### Why package nerds care For package nerds, Dependabot CLI is interesting because it exposes the machinery behind automated dependency PRs: ecosystem identifiers, manifest directory selection, registry credentials, update strategies, and the split between updater containers and a credential-injecting proxy. ### Timeline - 2022: Official dependabot/cli repository created. - 2022: README examples documented `dependabot update` and smoke-test workflows. - 2026: GitHub Docs continue to document dependabot.yml as the primary configuration surface for Dependabot. ### Related projects - Dependabot CLI depends conceptually on dependabot-core for package ecosystem behavior and on GitHub's dependabot.yml configuration model for hosted repository updates. ### Sources - - - ## Security Notes No matching local secret-handling manifest was found for dependabot. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: .github/dependabot.yml ## Combined YAML source View the package source record on GitHub. [combined/dependabot.yml](https://github.com/mxcl/pkgdb/blob/main/combined/dependabot.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph