Automic VaultAutomic Vault

brew

Install neverest with Homebrew, Nix

Synchronize, backup, and restore emails. Version 0.1.0 via Homebrew; verified 2026-05-19.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install neverest

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#neverest

nixpkgs package indexes · pkgs/by-name/ne/neverest/package.nix · source: api.github.com

overview

Package summary

Synchronize, backup, and restore emails

Commands and aliases

  • neverest

history

Project history and usage

Neverest is a Rust CLI for synchronizing, backing up, and restoring email. It belongs to the Pimalaya family of open-source personal-information-management tools.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

Risk level: blue

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

Risk classifier

blue risk · medium confidence · tool

Why

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

Signals

  • text:sync,backup

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 7 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Unix
$XDG_CONFIG_HOME/neverest/config.toml~/.config/neverest/config.toml~/.neverestrc

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
$XDG_CONFIG_HOME/neverest/config.toml~/.config/neverest/config.toml~/.neverestrc

executables

Installed executables

CommandKindExposureNote
neverestcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.1.0
manager updated2026-05-19
local dataok
upstreamcurrent
latest detectedv0.1.0

https://github.com/pimalaya/neverest

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:neverest
Version0.1.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/neverest
Homepagehttps://pimalaya.org
Repositoryhttps://github.com/pimalaya/neverest
Upstream docshttps://github.com/pimalaya/neverest#readme
LicenseMIT
Source archivehttps://github.com/pimalaya/neverest/archive/refs/tags/v0.1.0.tar.gz
Last updated2026-05-19T07:50:49-04:00
Pulseupdated
Build dependenciesrust
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameneverest
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

neverest

nix profile install nixpkgs#neverest
  • normalized package name match
  • Matched by: Neverest
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ne/neverest/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

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