Choose navi for executable recipes you can review
navi lets you browse cheatsheets, select suggested argument values and execute the resulting command. Choose it when that argument-selection step is useful enough to justify maintaining executable recipes. Its shell widget lets you edit a selected command before execution. Start with a small cheatsheet you understand and check the widget in your own shell before adding imported material.
The current navi README states that the project is in maintenance mode, with bug fixes continuing and no new features planned. This changes the adoption decision for teams that need future feature development. The notice is absent from the supplied README at our tested commit, so it should not be presented as an observation from that historical run. The current README recommends ezlo, but the supplied evidence does not establish its capabilities or migration requirements.
Our run recorded successful command outcomes
Our run on September 27, 2026 used commit 7389f95. The full revision was 7389f9544b9cbbf845acadb96c1b18a13ca988c4, and the compiler identified navi v2.25.0-beta1. Our sandbox used lab-rust:1 with 3 CPUs and a 12g memory limit. This was a source checkout, not a test of the v2.24.0 release binary.
The harness recorded an 18-second install step, a 42-second build step and a 19-second Cargo test step. Each returned exit code zero without a timeout. It stores success flags, exit codes, elapsed times, timeout status, parsed test summaries and log tails. The compiler's own build duration covers a narrower interval than the harness's whole build step; it does not replace the recorded build measurement.
The stored parser summaries report 52 passed, 0 failed and 52 total. The raw tail repeats Cargo suite footers after a replay marker. Those stored aggregates may therefore double-count results; unique and exhaustive counts were not verified. The visible suite footers report successful outcomes, but we neither sum them into a replacement total nor describe the stored aggregate as distinct passing tests.
We did not test an interactive picker session, shell-widget editing, Windows installation, imported cheatsheets or commands selected during a user's workflow. A zero exit code for Cargo tests does not establish those behaviors. No dependency audit result is attached, and scan coverage is unknown. The run provides no security assurance.
The MrKeyoor testing methodology explains how command outcomes and measurements reach a review. The supplied methodology page provides provenance context, rather than proof that its current procedure governed the September run. This correction uses the stored record; no new execution took place.
Review suggestion commands as well as the final recipe
The navi syntax guide describes executable command lines and variable definitions containing commands that generate possible argument values. A review must therefore cover both the command template and the commands used to populate its arguments. Inspecting only the completed command leaves part of the cheatsheet's behavior unchecked.
The widget's editing step is useful for checking what you are about to execute. It does not establish that imported recipes or suggestion commands are safe. Our sandbox did not reproduce a shell-injection report or verify a fix, and the supplied primary extracts do not establish the current status of the previously cited issues. This review makes no claim that those reports remain open or have been resolved.
Use reference sheets when lookup is enough
The tldr-pages project provides community-maintained help pages for command-line tools. Choose it when practical examples answer your question without needing navi's argument picker. It can also complement navi: the navi README documents using cheatsheets from tldr. Our run did not test that integration, so the documented connection is not a compatibility result.
cheat lets you create and view command-line cheatsheets. Its documentation also describes editing, tags, search and separate personal and community cheatpaths. Choose it when keeping and finding reference sheets meets your needs. We did not run either alternative; these decisions follow their documented roles rather than comparative setup, reliability or security measurements.
What the editorial ratings cover
The ratings use a 1-5 scale: 1 means substantial obstacles, 2 means limited support, 3 means usable with material constraints, 4 means strong support with caveats, and 5 means the strongest support within the stated assessment scope. They are editorial judgments, not benchmarks or adoption measurements.
Setup ease assesses the recorded source-build path, whose command steps completed successfully. Documentation assesses the supplied usage, installation and syntax instructions. Community assesses the documented provision of community packages and shared cheatsheets; it does not measure adoption, contributor responsiveness or support quality. Maturity weighs the successful historical command outcomes against the untested interactive workflow and current maintenance-only direction. None of these ratings establishes security or compatibility across shells and platforms.