Prefer upstream unless you explicitly need this fork’s older state; it shows no added capability and is materially behind on maintenance and fixes.
Prefer upstream unless you specifically need the Nushell template change and are comfortable carrying a stale fork; this fork adds little beyond that and is far behind upstream.
Choose upstream unless you specifically need this fork's namespace or a pinned snapshot; this fork does not add functionality and is already lagging slightly behind upstream.
Choose upstream unless you specifically need this exact fork snapshot; there is no added functionality here, only lag behind upstream.
dianecloud/zoxide
slowing
significant_divergence
Choose upstream if you want zoxide. Choose this fork only if you specifically want the forked email-service direction and are comfortable losing alignment with the original CLI project.
Prefer upstream unless you specifically need this exact snapshot. This fork adds no visible capabilities and is mainly useful as a pinned copy; adopters wanting current fixes or active maintenance should stay with upstream.
Prefer this fork only if you specifically need the Fish 4.1.x fix or its template behavior. For general use, upstream looks substantially more current and better maintained.
Prefer upstream. This fork shows no added functionality and is far behind, so it is mainly useful as a snapshot rather than as an improved distro.
Prefer upstream unless you specifically want this README wording. This fork is essentially upstream with one doc-only change and is materially behind, so it does not look like a better adoption target for functionality.
Prefer this fork if you specifically want the renamed `querypath` surface and its shell/documentation customization. Prefer upstream zoxide if you want the newest fixes, broader maintenance, and lower compatibility risk.