# Install himalaya with Homebrew, apk, MacPorts, Nix, pacman, scoop, zypper

CLI email client written in Rust. Version 1.2.0 via Homebrew; verified 2026-06-15.

## Install

```sh
sudo av install brew:himalaya
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install himalaya
```

  Evidence: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install himalaya
```

  Evidence: MacPorts ports tree: mail/himalaya/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- apk (92%):

```sh
sudo apk add himalaya
```

  Evidence: Alpine Linux edge package indexes: himalaya from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

- Nix (92%):

```sh
nix profile install nixpkgs#himalaya
```

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

- pacman (92%):

```sh
sudo pacman -S himalaya
```

  Evidence: Arch Linux sync databases: himalaya from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install himalaya
```

  Evidence: openSUSE Tumbleweed package metadata: himalaya from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst

### Windows

- Scoop (92%):

```sh
scoop install main/himalaya
```

  Evidence: Scoop official bucket manifest trees: bucket/himalaya.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:himalaya
- **Package manager:** Homebrew
- **Package manager page:** <https://formulae.brew.sh/formula/himalaya>
- **Version:** 1.2.0
- **Source summary:** CLI email client written in Rust
- **Homepage:** <https://pimalaya.org>
- **Repository:** <https://github.com/pimalaya/himalaya>
- **Upstream docs:** <https://github.com/pimalaya/himalaya#readme>
- **License:** MIT
- **Source archive:** <https://github.com/pimalaya/himalaya/archive/refs/tags/v1.2.0.tar.gz>
- **Last updated:** 2026-06-15T10:20:18-04:00
- **Generated:** 2026-07-08T07:18:31+00:00

## Executables

- himalaya (cli)
- himalaya (alias)

## Build dependencies

- pkgconf
- rust

## Install behavior

- Post-install hook: not defined
- Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 1.2.0
- Package-manager updated: 2026-06-15
- Local data: ok
- Upstream repository: https://github.com/pimalaya/himalaya
- Upstream latest detected: v1.2.0 (current)
## Project history and usage

Himalaya is a Rust command-line email client from the Pimalaya family of personal information management tools. Its package-manager identity is a terminal-native mail workflow: install one binary, configure accounts in TOML, and script mailbox, envelope, message, attachment, IMAP, SMTP, JMAP, Gmail, Microsoft Graph, Maildir, and m2dir operations from the shell.

The project fits a long Unix tradition of separating mail transport, storage, composition, and viewing into composable tools. Himalaya's particular contribution is to make modern email protocols and JSON output feel natural in a CLI package, while sharing configuration and libraries with other Pimalaya interfaces.

### Project history

The public repository begins on 2020-12-24 with commits that initialized the project and its TOML configuration parser. Within the first days of development, the repository added IMAP connection handling, email listing, command-line parsing, mailbox listing, text and HTML previews, SMTP setup, and message writing, showing that the initial scope was already a full read-write email client rather than only a message viewer.

The first tagged release, v0.1.0, appeared on 2021-01-17. Through the 0.x series, the project expanded around mailbox, envelope, flag, message, and attachment operations. A v1 series followed, with v1.0.0 tagged in 2024 and v1.2.0 tagged in 2026.

The Pimalaya site describes the larger effort as Rust libraries and applications for personal information management, including email, contacts, calendars, tasks, and timers. Himalaya's later v2 migration notes place the CLI inside that broader architecture: protocol logic moved toward I/O-free libraries, OAuth moved into ortie, keyring handling moved into mimosa, message composition moved into mml, and session reuse moved into syrup.

### Adoption history

Himalaya reached several package ecosystems because it solves a concrete terminal-user problem: email automation without a graphical client. The README documents installation through Homebrew, Arch Linux, Scoop, Fedora/CentOS/RHEL COPR, Nix flakes, Cargo, pre-built GitHub binaries, and source builds.

Its adoption story is strongest among users who want mail in editor, shell, and script workflows. Pimalaya also lists companion interfaces such as himalaya-tui, and the Himalaya README notes that the CLI and TUI share the same account configuration blocks. That makes the package useful both as a direct CLI and as a backend for richer terminal interfaces.

### How it is used

Himalaya loads persistent account configuration from XDG and legacy Unix paths, supports a configuration wizard, and uses TOML account blocks. The README documents provider-oriented examples for Proton Mail, Gmail, Outlook, and iCloud Mail, including command-backed secrets and OAuth token helpers.

The CLI exposes a shared API for common mail concepts and protocol-specific APIs for native backend capabilities. It can emit JSON, so package users can compose it with jq, fzf, editor commands, notification scripts, and other terminal automation.

### Why package nerds care

For package nerds, Himalaya is interesting because it turns email into a scriptable Rust CLI while still respecting the complexity of real email providers. It carries the usual package-manager virtues: a single executable, documented config locations, multiple install channels, and well-scoped optional build features.

The v2 migration is also a useful case study in CLI maintainability. The maintainers explicitly removed over-broad backend abstraction from the CLI and pushed protocol, auth, composition, keyring, and session-reuse concerns into smaller tools and libraries. That kind of decomposition matters to downstream packagers because it clarifies what the packaged binary is responsible for.

### Timeline

- 2020-12-24: Public repository history begins with project initialization and TOML config parsing.
- 2021-01-17: v0.1.0 is tagged.
- 2021: Early releases add mailbox, envelope, IMAP, SMTP, and message-management functionality.
- 2022: Pimalaya is described as an organized PIM effort around Rust libraries and applications.
- 2024: v1.0.0 is tagged.
- 2026: v1.2.0 is tagged, and v2 migration notes document a split into smaller Pimalaya libraries and helper tools.

### Related projects

- Pimalaya is the umbrella project for the Rust PIM libraries and applications around Himalaya.
- himalaya-tui is a terminal interface that shares Himalaya account configuration.
- ortie, mimosa, mml, and syrup are Pimalaya tools or libraries referenced by the migration guide for OAuth, password access, message composition, and session reuse.
- Traditional adjacent tools include mutt/neomutt, mbsync/isync, OfflineIMAP, notmuch, and maildir-based workflows, although Himalaya's official docs emphasize its own protocol backends rather than positioning it as a clone of any one of them.

### Sources

- Official Git repository tags and commits for timeline dates.
- Official Himalaya migration guide for v1-to-v2 architectural evolution.
- Official Himalaya repository README for feature, install, configuration, and backend details.
- Official Pimalaya website for project scope and founding context.


## Security Notes

broad file, network, media, or database tool signal.

- **Geiger risk:** blue / medium
- broad file, network, media, or database tool signal


## 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: $XDG_CONFIG_HOME/himalaya/config.toml, ~/.config/himalaya/config.toml, ~/.himalayarc
## Source Database Details

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

## Other Package-Manager Records

- Nix - himalaya: normalized package name match | nixpkgs package indexes: pkgs/by-name/hi/himalaya/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- apk - himalaya - 1.2.0-r0: normalized package name match | Alpine Linux edge package indexes: himalaya from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | CLI email client | https://github.com/soywod/himalaya
- apk - himalaya-bash-completion - 1.2.0-r0: normalized package name match | Alpine Linux edge package indexes: himalaya-bash-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Bash completions for himalaya | https://github.com/soywod/himalaya
- apk - himalaya-doc - 1.2.0-r0: normalized package name match | Alpine Linux edge package indexes: himalaya-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | CLI email client (documentation) | https://github.com/soywod/himalaya
- apk - himalaya-fish-completion - 1.2.0-r0: normalized package name match | Alpine Linux edge package indexes: himalaya-fish-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Fish completions for himalaya | https://github.com/soywod/himalaya
- apk - himalaya-zsh-completion - 1.2.0-r0: normalized package name match | Alpine Linux edge package indexes: himalaya-zsh-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Zsh completions for himalaya | https://github.com/soywod/himalaya
- pacman - himalaya - 1.2.0-1: normalized package name match | Arch Linux sync databases: himalaya from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A CLI email client | https://github.com/soywod/himalaya
- zypper - himalaya - 1.2.0-1.4: normalized package name match | openSUSE Tumbleweed package metadata: himalaya from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | Command-line interface for email management | https://github.com/pimalaya/himalaya
- MacPorts - himalaya: normalized package name match | MacPorts ports tree: mail/himalaya/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Scoop - main/himalaya: normalized package name match | Scoop official bucket manifest trees: bucket/himalaya.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Related links

- [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals.
- [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata.
- [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [pkgconf](https://www.automicvault.com/pkg/brew/pkgconf/) - Build dependency declared by Homebrew.
- [rust](https://www.automicvault.com/pkg/brew/rust/) - Build dependency declared by Homebrew.
- [neverest](https://www.automicvault.com/pkg/brew/neverest/) - Shares the same upstream homepage.
- [neomutt](https://www.automicvault.com/pkg/brew/neomutt/) - Shares av.db curated category or tags: cli, email, imap, productivity, smtp.
- [mailcheck](https://www.automicvault.com/pkg/brew/mailcheck/) - Shares av.db curated category or tags: cli, email, imap, productivity.
- [meli](https://www.automicvault.com/pkg/brew/meli/) - Shares av.db curated category or tags: cli, email, imap, productivity.
- [nmail](https://www.automicvault.com/pkg/brew/nmail/) - Shares av.db curated category or tags: cli, email, imap, productivity, smtp.
- [offlineimap](https://www.automicvault.com/pkg/brew/offlineimap/) - Shares av.db curated category or tags: cli, email, imap, productivity.
- [pop](https://www.automicvault.com/pkg/brew/pop/) - Shares av.db curated category or tags: cli, email, productivity, smtp.
- [aerc](https://www.automicvault.com/pkg/brew/aerc/) - Shares av.db curated category or tags: cli, email, productivity.

## Combined YAML source

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


## Sources

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated configuration and credential file locations
- 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
