# Install tach with Homebrew

Tool to enforce dependencies using modular architecture. Version 0.35.0 via Homebrew; verified 2026-07-25.

## Install

```sh
sudo av install brew:tach
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install tach
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:tach
- **Package manager:** Homebrew
- **Version:** 0.35.0
- **Source summary:** Tool to enforce dependencies using modular architecture
- **Homepage:** <https://docs.gauge.sh/getting-started/introduction>
- **Repository:** <https://github.com/tach-org/tach>
- **Last updated:** 2026-07-25T10:58:07Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- tach (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Tach is a Python architecture-enforcement CLI that checks imports against declared module boundaries and public interfaces. Its official documentation frames it as a tool for pre-commit hooks, CI checks, and incremental adoption in existing Python repositories.

### Project history

The public GitHub repository was created in January 2024, and the project presents itself as a Rust-written tool for Python dependency and interface enforcement. The official docs describe `tach.toml` as the root project configuration and `tach.domain.toml` as an optional per-domain configuration file for teams that want ownership closer to module code.

### Adoption history

Tach's adoption story is centered on normal developer-tool channels: pip installation, Homebrew packaging, pre-commit hooks, CI, and VS Code integration. The repository metadata and documentation emphasize incremental adoption, which matters for large Python codebases where architecture checks must coexist with existing imports before being tightened.

### How it is used

Typical use starts with `tach init`, then `tach check` in local workflows or CI. Other commands visualize dependency graphs, synchronize configuration with observed imports, check external package dependencies, generate dependency maps, and run impacted tests.

### Why package nerds care

Package-manager users care about Tach because it turns package/module boundaries into a checked artifact that can travel with a repository. It sits in the same practical space as linters and type checkers: installable as a CLI, cheap enough for hooks, and useful for enforcing dependency contracts before packaging or deployment.

### Timeline

- 2024: Public GitHub repository created.
- 2024: Official docs describe Tach as open source, pip-installable, CI-friendly, and incrementally adoptable.
- 2026: Homebrew formula metadata lists `tach` as a package-manager-distributed CLI.

### Related projects

- Tach relates to Python linters, import-boundary checkers, pre-commit hooks, CI dependency checks, and monorepo tooling.

### Sources

- <https://api.github.com/repos/tach-org/tach>
- <https://docs.gauge.sh/getting-started/introduction>
- <https://docs.gauge.sh/usage/configuration/>
- <https://github.com/tach-org/tach>
- source_facts.package-manager


## Security Notes

No matching local secret-handling manifest was found for tach. 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: tach.toml, tach.domain.toml

## Combined YAML source

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