# Install transcrypt with Homebrew

Configure transparent encryption of files in a Git repo. Version 2.3.2 via Homebrew; verified 2026-05-18.

## Install

```sh
sudo av install brew:transcrypt
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install transcrypt
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:transcrypt
- **Package manager:** Homebrew
- **Version:** 2.3.2
- **Source summary:** Configure transparent encryption of files in a Git repo
- **Homepage:** <https://github.com/elasticdog/transcrypt>
- **Repository:** <https://github.com/elasticdog/transcrypt>
- **Last updated:** 2026-05-18T14:24:55Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- transcrypt (alias)

## Install behavior

- Bottle: not available

## Freshness

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

transcrypt is a Bash-based Git encryption helper that configures transparent encryption and decryption for selected files in a repository. It is aimed at teams that want secrets, private keys, or other sensitive files versioned without exposing plaintext in remotes.

### Project history

The project was built around Git clean and smudge filters, following the same broad model as git-crypt and git-encrypt while emphasizing usability and safety. Its README highlights that it is a Bash script, uses OpenSSL symmetric ciphers, does not need to remain installed after repository configuration, and adds checks to avoid clobbering existing configuration.

Official release metadata shows active maintenance from at least the 1.x era in 2018 through the 2.x line, with v2.3.2 released in 2026.

### Adoption history

transcrypt's official installation notes document both manual installation and package-manager availability. The project lists Arch Linux, Heroku buildpacks, NixOS, OS X via Homebrew, and FreeBSD packages, which points to adoption by developers who want repository-local encryption available through standard system tooling.

### How it is used

A typical workflow initializes transcrypt inside a Git repository, marks paths in `.gitattributes` with the crypt filter, commits encrypted versions of selected files, and shares the cipher and password with trusted clones. The README also documents listing encrypted files, checking raw committed contents, initializing a clone, rekeying, flushing credentials, and uninstalling repository configuration.

### Why package nerds care

For package nerds, transcrypt is a compact alternative to heavier secret-management systems when the requirement is simply encrypted files in Git. Because it is a single script using Bash, Git, and OpenSSL, distribution packages mostly provide convenient installation, shell completion, and man-page style polish rather than a runtime service.

### Timeline

- 2015: The install guide notes that the NixOS derivation was added in October 2015.
- 2018: Official GitHub releases include the 1.x series.
- 2026: Official GitHub releases list transcrypt v2.3.2.

### Related projects

- The README explicitly compares transcrypt with git-crypt and git-encrypt, all of which use Git filters to encrypt selected repository contents.

### Sources

- <https://api.github.com/repos/elasticdog/transcrypt/releases>
- <https://github.com/elasticdog/transcrypt#readme>
- <https://github.com/elasticdog/transcrypt/blob/main/INSTALL.md>


## Security Notes

No matching local secret-handling manifest was found for transcrypt. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Combined YAML source

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


## Sources

- Nucleus package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
