/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

casey/just

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T16:04:30.478Z

1mo ago

casey/just

`casey/just` is a Rust command runner for project-specific commands stored in `justfile`s. It is active, widely used, and frequently updated, with 32,478 stars, 705 forks, and recent commits on 2026-03-30. The repository includes core source, tests, docs/book content, completions, examples, and Nix support.

Loading tags...

Stars32,478

Forks705

Default branchmaster

Last pushed2026-03-30T06:38:17Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if its added testing and recipe-behavior changes are exactly what you need and you can tolerate being far behind upstream. For most adopters, upstream `casey/just` is the safer choice because this fork looks stale and materially diverged.

Prefer upstream `casey/just` unless you specifically need this fork's syntax and CLI experiments. This fork looks useful for customization work, but it is too stale and too diverged to recommend as the default choice for most users.

Choose this fork if you want a container/release-focused `just` distribution and can tolerate upstream lag. Prefer upstream if you want the newest CLI behavior, fixes, and documentation.

Prefer upstream unless you intentionally need this older, unmodified snapshot. It adds no visible capabilities and is materially behind on fixes, CLI polish, and packaging updates.

Choose this fork only if you want the translated docs and web presence; choose upstream if you care about current functionality, bug fixes, or long-term maintainability.

Prefer upstream `casey/just` unless you specifically need this frozen snapshot. This fork does not add capabilities and is substantially behind current upstream.

Prefer upstream unless you specifically need this older snapshot as a base for your own work. The fork adds nothing visible and is materially behind on recent fixes and tooling improvements.

Prefer upstream unless you specifically need a pinned historical snapshot. This fork adds no visible features and is 78 commits behind, so it looks like a stale mirror rather than a differentiated distribution.

Prefer upstream unless you specifically need this exact older snapshot; the fork adds no visible capabilities and is significantly behind current `just`.

Choose upstream unless you specifically need this exact older snapshot; this fork appears dormant and adds no user-facing advantages.

Fork comparison

hiroyukikumazawa/just

38/100

stale

significant_divergence

Prefer this fork only if its added testing and recipe-behavior changes are exactly what you need and you can tolerate being far behind upstream. For most adopters, upstream `casey/just` is the safer choice because this fork looks stale and materially diverged.

Likely purpose

A customized fork of the `just` command runner that seems to focus on earlier CLI UX, extra recipe/settings behavior, and test-driven local modifications rather than staying current with upstream releases.

Best for

Users who specifically want the fork's added recipe/testing and working-directory behavior.; Maintainers who need a customized `just` derivative for a controlled environment.; Developers willing to trade upstream freshness for fork-specific workflow changes.; People evaluating a legacy snapshot rather than the current upstream tool.

Additional features

Adds a `--request` subcommand for testing.
Adds `[working-directory]` recipe behavior.
Adds `--allow-missing` to ignore missing recipe and submodule errors.
Adds `[openbsd]` recipe attribute support.
Improves help text styling and error presentation.
Includes formatting and parser changes around config, invocation parsing, and recipe handling.

Missing features

Lags upstream by roughly 200 commits behind and appears to miss many 2026 upstream changes.
Likely misses recent upstream CLI and runtime improvements such as `--indentation`, verbose recipe path output, and the latest shell/completion fixes.
Large deletions in `tests/options.rs`, `tests/settings.rs`, and `src/invocation_parser.rs` suggest some upstream behaviors or coverage were removed or are harder to rely on.
Because the fork is stale, adopters should expect gaps in newer release and documentation updates.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

May appeal to users who want a more opinionated or experimental `just` variant.
Adds workflow-oriented options for testing, missing-path tolerance, and working-directory control.
Could be attractive if you need OpenBSD-specific or custom recipe metadata support.
The fork has concrete local changes rather than being a no-op mirror.

Risks

Stale activity is the biggest risk: it was last pushed in 2024 while upstream is active in 2026.
High divergence makes upstream bugfixes, docs, and release behavior harder to trust.
Large deletions raise the chance of compatibility regressions or missing edge-case coverage.
Adopting it as a general-purpose replacement likely means giving up newer upstream fixes and maintenance cadence.

casey/just · Discofork