Installer neverest avec Homebrew, Nix

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• neverest

Historique du projet

The Neverest repository was initialized in April 2024. Its release feed records a `root` tag on 2024-04-10, v0.1.0 on 2024-04-15, and v1.0.0-beta shortly after. The v0.1.0 release note says the project was initiated from Himalaya CLI, which explains its place in the Pimalaya email-tool split.

Historique d'adoption

Neverest remains early and very niche as a packaged tool. GitHub showed roughly 310 stars and 11 forks when researched on 2026-07-01, while the Homebrew formula still packaged stable 0.1.0 and reported only 27 install-on-request events over 365 days.

Modes d'utilisation

The upstream main-branch README documents unreleased v1 behavior and explicitly warns that v1 is not yet released, while Homebrew packages v0.1.0. The v1 docs describe IMAP, JMAP, and local m2dir backends; account initialization; `neverest sync`; dry runs; mailbox filters; per-side permissions; and an incremental cache under `$XDG_CACHE_HOME/neverest/<account>/state.json`.

For package nerds, the important bit is the backend model: Neverest is not just a mail fetcher, but a bidirectional sync engine with explicit local/remote sides and conservative controls for create/delete/update behavior. The packaging lag means users need to check which command surface their installed version actually exposes.

Pourquoi les passionnés de paquets s'y intéressent

Neverest is significant inside the Pimalaya ecosystem because email sync moved out of Himalaya into a focused CLI. Outside that ecosystem, source evidence supports calling it experimental rather than widely adopted.

Chronologie

• 2024-04-10: Release feed shows initial `root` tag.
• 2024-04-15: v0.1.0 release note says Neverest was initiated from Himalaya CLI.
• 2024-09-03: Release feed shows v1.0.0-beta update.
• 2026-07-01: Homebrew formula API reported stable 0.1.0 and 27 install-on-request events over 365 days.

Related projects

• Himalaya CLI is the parent/sibling email CLI from which Neverest's sync scope was split.
• Mirador is another Pimalaya CLI split focused on watching mailbox changes.
• m2m is referenced by Neverest as a Maildir-to-m2dir migration helper.

Sources

• https://formulae.brew.sh/api/formula/neverest.json
• https://formulae.brew.sh/formula/neverest
• https://github.com/pimalaya/neverest
• https://github.com/pimalaya/neverest/releases.atom
• https://github.com/pimalaya/neverest/releases/tag/v0.1.0
• https://pimalaya.org/
• https://raw.githubusercontent.com/pimalaya/neverest/master/README.md