# Install all-repos with Homebrew

Clone all your repositories and apply sweeping changes. Version 1.32.0 via Homebrew; verified 2026-05-13.

## Install

```sh
sudo av install brew:all-repos
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install all-repos
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:all-repos
- **Package manager:** Homebrew
- **Version:** 1.32.0
- **Source summary:** Clone all your repositories and apply sweeping changes
- **Homepage:** <https://github.com/asottile/all-repos>
- **Last updated:** 2026-05-13T17:53:26Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- all-repos-clone (alias)
- all-repos-complete (alias)
- all-repos-find-files (alias)
- all-repos-grep (alias)
- all-repos-list-repos (alias)
- all-repos-manual (alias)
- all-repos-sed (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.32.0
## Project history and usage

all-repos is Anthony Sottile's command-line toolkit for cloning many repositories and applying sweeping searches or changes across them.

### Project history

The public repository begins in git history on 2017-08-02 with an initial skeleton, followed by v0.1.0 on 2017-08-04 and v1.0.0 on 2017-10-24. The README describes the package as a pip-installable CLI suite rather than a single command.

The tool grew around a simple configuration file, all-repos.json, that chooses a repository source module and optional push module. Built-in modules cover sources such as GitHub and file-based repository lists, while push modules can open pull requests.

### Adoption history

The input package-manager facts show Homebrew packaging. The README's primary installation path is pip, which matches its Python ecosystem audience and its use in multi-repository maintenance workflows.

### How it is used

Users run all-repos-clone to materialize or update every configured repository, then use tools like all-repos-grep, all-repos-find-files, all-repos-sed, and all-repos-manual to inspect or modify the fleet. The default config filename is all-repos.json and can be overridden with -C or ALL_REPOS_CONFIG_FILENAME.

The README documents API keys in source_settings or push_settings, with api_key_env alternatives for keeping tokens in the environment.

### Why package nerds care

all-repos is a concise answer to the monorepo-versus-many-repos maintenance problem: it gives package maintainers and infra engineers a scriptable way to fan out searches, sed edits, and pull requests across repositories without adopting a larger platform.

### Timeline

- 2017: Public Git history begins.
- 2017: v0.1.0 and v1.0.0 tags appear.
- 2026: v1.32.0 tag appears in repository history.

### Related projects

- git: underlying clone, grep, and repository operation tool.
- GitHub, GitLab, Bitbucket, and Azure Repos: repository providers supported through source and push modules.

### Sources

- Git history from https://github.com/asottile/all-repos.git
- Official README: https://raw.githubusercontent.com/asottile/all-repos/main/README.md
- source_facts.package-manager


## Security Notes

No matching local secret-handling manifest was found for all-repos. 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: all-repos.json

## Credential files

- Unix: all-repos.json

## Combined YAML source

View the package source record on GitHub. [combined/all-repos.yml](https://github.com/mxcl/pkgdb/blob/main/combined/all-repos.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