zoxide is a free command-line tool that makes cd smarter. It remembers the folders you visit, and after that you type z and a few letters of the name, such as z proj, to land in the best match, ranked by how often and how recently you use it. zi opens an interactive picker with fzf when several folders match.
It earns its place because it saves a lot of typing for almost no setup: one program and one line in your shell's config file. It works in bash, zsh, fish, PowerShell, Nushell, Elvish and more, can import your history from older jump tools such as autojump, z and fasd, and file managers such as yazi use it too. With the --cmd cd option you can keep typing cd and still get zoxide's jumps.
zoxide is MIT-licensed and written in Rust by Ajeet D'Souza, who started it in 2020. It has about 40,600 stars and around 120 contributors. Version 0.10.0 came out on 4 July 2026.
- Repository: github.com/ajeetdsouza/zoxide
- Licence: MIT (MIT License)
- Language: Rust. Stars: 40.6K. Forks: 953. Last push: Nov 8, 2026.
- Scan: safe, Nov 16, 2026, commit 1bb0620
Who it is for
Developers, sysadmins and anyone who moves between the same project folders all day in a terminal. It works on macOS, Linux and Windows; you need to add one line to your shell config.
Getting started
1. Install on macOS or Linux with Homebrew
brew install zoxide2. Or on Windows, with winget
winget install ajeetdsouza.zoxide3. Turn it on for zsh, then open a new terminal (for bash, add eval "$(zoxide init bash)" to ~/.bashrc)
echo 'eval "$(zoxide init zsh)"' >> ~/.zshrc4. Visit folders with cd as usual, then jump back with a few letters of the name
z proj5. Pick from every match interactively (needs fzf)
zi projPackage managers do not change your shell files; the line you add does. The install script for macOS and Linux puts the program in ~/.local/bin and asks for sudo only if it cannot write there. The folder list lives in a small local database, on macOS in ~/Library/Application Support/zoxide. Our scan covers the source code, not the prebuilt binaries.
Safety scan
We cloned ajeetdsouza/zoxide at commit 1bb0620 on Nov 16, 2026 and ran the checks described on the GitHub Tools page: credential patterns, decode-and-execute code, install-time scripts, committed binaries, risky CI workflows, every host the code talks to, known vulnerabilities in pinned dependencies, and project hygiene. A person read every hit. This is what we found.
- 0 secret hits and no committed binaries across 74 files and about 5,900 lines: Rust, plus the shell templates zoxide prints for each shell.
- 0 pattern hits. The hook that zoxide init adds to your shell only records the folder you move into. build.rs only generates the shell completion files.
- install.sh is about 470 lines. It downloads the release archive for your system from GitHub with curl or wget and copies the program into ~/.local/bin and its manual into ~/.local/share/man, using sudo only when it cannot write there. It does not edit your shell files.
- 3 advisories with no severity rating, all in Rust libraries in Cargo.lock: an unsoundness bug in anyhow, a notice that bincode is no longer maintained, and a memory-correctness bug in rustix. None is rated high or critical.
- The program contacts no server; the hosts in the code are GitHub links for the installer. Five workflows, no pull_request_target, but none of the 18 third-party actions is pinned to a commit. Releases go to crates.io through its trusted publishing. Dependabot is on; no security policy file or CodeQL. OpenSSF Scorecard gives it 4.4 out of 10.
What the scanner counted
| Check | Result |
|---|---|
| Secrets | None found. |
| Suspicious code | None found. |
| Install-time code | 1 Cargo build script. 1 installer script (one can call sudo) |
| Committed binaries | None. |
| CI workflows | 5 workflows. None use pull_request_target. 18 of 18 third-party actions pinned to a tag rather than a commit. |
| Network hosts | 2 distinct hosts referenced from source; most often github.com, api.github.com. No URLs to bare IP addresses. |
| Known vulnerabilities | 3 advisories across 128 pinned packages: 0 critical, 0 high, 0 moderate, 0 low, 3 unrated. Cargo.lock: 128 packages, 3 advisories. |
| Project hygiene | Has automated dependency updates, licence file. Missing security policy, CodeQL, contributing guide. |
| OpenSSF Scorecard | 4.4 out of 10, as of Nov 9, 2026. |
The raw findings
Every hit the scanner wrote out, with a link to the exact line at the scanned commit. Secrets candidates are redacted.
Installer scripts (1)
- install.sh, 467 lines, uses sudo; talks to api.github.com, github.com
Worst known vulnerabilities (3 of 3)
| Advisory | Severity | Package | Summary |
|---|---|---|---|
| RUSTSEC-2026-0190 | unknown | anyhow@1.0.102 | Unsoundness in `Error::downcast_mut()` |
| RUSTSEC-2025-0141 | unknown | bincode@1.3.3 | Bincode is unmaintained |
| GHSA-jh2m-fhpj-3vr7 | unknown | rustix@1.1.4 | xattr functions mark unwritten bytes as initialized when given a zero-length buffer |
By the numbers
| Stars | 40.6K |
|---|---|
| Forks | 953 |
| Contributors | 118 |
| Commits | 661 |
| Open issues | 99 |
| Open pull requests | 59 |
| Releases | 38 |
| Latest release | v0.10.0 |
| Licence | MIT |
| Main language | Rust |
| Project age | 6 years |
| Last push | Nov 8, 2026 |
| Tracked files | 74 |
| Lines of code | 5,937 |
| Checkout size | 935 KB |
Lines by language: Rust 2,828, Markdown 1,326, Shell 822, TypeScript 394, YAML 252, PowerShell 185.
Questions
Is zoxide free?
Yes. It is free and open source under the MIT licence, with no paid version. The README shows sponsor logos for Warp and Recall.ai.
zoxide or cd?
Both. Keep cd for exact paths and use z when you know roughly where you are going. If you want one command, set it up with --cmd cd and cd itself gets zoxide's jumps.
Does zoxide work on Windows?
Yes. Install it with winget, Scoop or Chocolatey, add the line from the README to your PowerShell profile, and z works there too.
Does zoxide send my data anywhere?
No. It keeps the folders you visit in a local database file and never goes online. zoxide remove deletes a folder from it, and the _ZO_EXCLUDE_DIRS setting keeps folders out.
How do I uninstall zoxide?
Remove the zoxide init line from your shell config, run brew uninstall zoxide or winget uninstall ajeetdsouza.zoxide, and delete its data folder if you want the history gone.
This post is part of GitHub Tools, where every repository is cloned and scanned before it is written up. The scan is a snapshot of one commit on one day; the repository has moved on since, so check it before you install.
