# Install bashate with Homebrew, Nix

Code style enforcement for bash programs. Version 2.1.1 via Homebrew; verified 2026-06-15.

## Install

```sh
sudo av install brew:bashate
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install bashate
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#bashate
```

  Evidence: nixpkgs package indexes: pkgs/by-name/ba/bashate/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:bashate
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/bashate>
- **Version:** 2.1.1
- **Source summary:** Code style enforcement for bash programs
- **Homepage:** <https://opendev.org/openstack/bashate>
- **Repository:** <https://opendev.org/openstack/bashate>
- **Upstream docs:** <https://docs.openstack.org/bashate/latest>
- **License:** Apache-2.0
- **Source archive:** <https://files.pythonhosted.org/packages/4d/0c/35b92b742cc9da7788db16cfafda2f38505e19045ae1ee204ec238ece93f/bashate-2.1.1.tar.gz>
- **Last updated:** 2026-06-15T10:20:10-04:00
- **Generated:** 2026-07-09T07:20:21+00:00

## Executables

- bashate (cli)
- bashate (alias)

## Dependencies

- python@3.14

## Install behavior

- Post-install hook: not defined
- Bottle: available on all

## Freshness

- Page generated: 2026-07-09
- Package-manager version: 2.1.1
- Package-manager updated: 2026-06-15
- Local data: ok
- Upstream repository: https://opendev.org/openstack/bashate
- info: Release/tag comparison is only available for GitHub repositories.
## Project history and usage

bashate is OpenStack's style checker for Bash scripts. It is essentially a pycodestyle-style lint gate for shell code, built for projects where Bash scripts are part of the reviewed and tested codebase.

### Project history

The official README calls bashate a pep8 equivalent for Bash scripts and says it attempts to fill the same automated code-review role for Bash that pep8 did in many OpenStack projects. It also states that bashate started in the DevStack project and would continue to evolve over time.

The OpenStack documentation and Opendev source identify it as an Apache-licensed OpenStack project with docs, source, bugs, release notes, and contribution pages. Its documented checks cover whitespace, indentation, line endings, line length, structure rules, `bash -n` syntax errors, and obsolete or unsafe syntax.

### Adoption history

bashate's adoption is tied to OpenStack's large shell-script surface, especially DevStack and project automation. The batch input shows Homebrew and Nix packaging; in practice, the tool is most valuable to contributors and CI jobs enforcing OpenStack-adjacent shell style.

The release notes and official tag list show a 0.x line followed by 1.0.0 and 2.x releases, enough history to treat it as a maintained OpenStack utility rather than a one-off script.

### How it is used

Users run `bashate` against shell scripts to catch style and safety issues before review or CI. Its output intentionally follows the default pycodestyle output format, making it familiar in OpenStack's Python-heavy review culture.

The documented checks include trailing whitespace, hard tabs, non-multiple-of-four indents, missing final newline, missing shebang or `.sh` suffix, long lines, malformed control structures, heredoc termination, function declaration style, `bash -n` syntax errors, deprecated `$[` arithmetic, risky `local` declarations, and `[[` recommendations for comparisons.

### Why package nerds care

bashate is package-nerd significant because it shows shell scripts becoming first-class reviewed artifacts in a large infrastructure project. It is not a general-purpose shell parser revolution; it is the small enforcement tool that makes a project's Bash style reproducible across laptops and CI workers.

It also captures an OpenStack packaging pattern: a narrow Python CLI published as a standalone package, documented by Sphinx, hosted in Opendev, and installed by package managers for repeatable developer workflows.

### Timeline

- 2010s: bashate starts in the DevStack project, according to the official README.
- 2010s: 0.x release tags establish the early style-checker line.
- 2020: OpenStack release-notes build documents the 0.5.x, 0.6.0, and 1.0.0 release notes.
- 2020s: Official tag list reaches the 2.x release line.
- 2020s: Homebrew and Nix package the `bashate` CLI.

### Related projects

- Related projects include DevStack, OpenStack's broader CI/review tooling, pycodestyle/pep8, ShellCheck, shfmt, and Bash itself. bashate's own README explicitly compares its role to pycodestyle.

### Sources

- Official Opendev tag list shows 0.1.0 through 2.1.1 tags.
- Official README says bashate is a pep8 equivalent for Bash scripts, started in DevStack, and follows pycodestyle output format.
- Official docs list project documentation, source, bug tracker, release notes, contributing docs, and supported checks.
- Official release notes page documents 0.5.x, 0.6.0, and 1.0.0 notes.
- input.source_facts.package-manager lists Homebrew and Nix packaging.


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals

## Source Database Details

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** bashate
- **Version Scheme:** 0
- **Revision:** 2
- **Head Version:** HEAD
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** head, stable

## Other Package-Manager Records

- Nix - bashate: normalized package name match | nixpkgs package indexes: pkgs/by-name/ba/bashate/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Related links

- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata.
- [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [python@3.14](https://www.automicvault.com/pkg/brew/python-3-14/) - Runtime dependency declared by Homebrew.
- [checkbashisms](https://www.automicvault.com/pkg/brew/checkbashisms/) - Shares av.db curated category or tags: cli, developer-tools, linting, shell.
- [cpplint](https://www.automicvault.com/pkg/brew/cpplint/) - Shares av.db curated category or tags: cli, developer-tools, linting, style-checker.
- [editorconfig-checker](https://www.automicvault.com/pkg/brew/editorconfig-checker/) - Shares av.db curated category or tags: cli, developer-tools, linting, style-checker.
- [markdownlint-cli](https://www.automicvault.com/pkg/brew/markdownlint-cli/) - Shares av.db curated category or tags: cli, developer-tools, linting, style-checker.
- [markdownlint-cli2](https://www.automicvault.com/pkg/brew/markdownlint-cli2/) - Shares av.db curated category or tags: cli, developer-tools, linting, style-checker.
- [shellcheck](https://www.automicvault.com/pkg/brew/shellcheck/) - Shares av.db curated category or tags: bash, cli, developer-tools, linting, shell.
- [actionlint](https://www.automicvault.com/pkg/brew/actionlint/) - Shares av.db curated category or tags: cli, developer-tools, linting.
- [bpmnlint](https://www.automicvault.com/pkg/brew/bpmnlint/) - Shares av.db curated category or tags: cli, developer-tools, linting.
- [git-review](https://www.automicvault.com/pkg/brew/git-review/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, code, developer, developer-tools, python.
- [cmake-lint](https://www.automicvault.com/pkg/brew/cmake-lint/) - Both packages touch the same language runtime or ecosystem. Shared terms: checker, cli, code, developer, developer-tools.

## Combined YAML source

View the package source record on GitHub. [combined/bashate.yml](https://github.com/automic-vault/db/blob/main/combined/bashate.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
