Skip to content

Installation

Terminal window
cargo install skif-cli
# or, to download a prebuilt binary:
cargo binstall skif-cli

The skif crate is the library and has no binary, so cargo install skif fails. The command-line tool is skif-cli.

Each release attaches one archive per target, plus checksums.txt.

Target Archive
macOS, Apple silicon / Intel skif-aarch64-apple-darwin.tar.gz, skif-x86_64-apple-darwin.tar.gz
Linux x64 / arm64, glibc skif-x86_64-unknown-linux-gnu.tar.gz, skif-aarch64-unknown-linux-gnu.tar.gz
Linux x64 / arm64, musl (static, Alpine) skif-x86_64-unknown-linux-musl.tar.gz, skif-aarch64-unknown-linux-musl.tar.gz
Windows x64 / arm64 skif-x86_64-pc-windows-msvc.zip, skif-aarch64-pc-windows-msvc.zip

Each archive holds the skif binary (skif.exe on Windows), the LICENSE and the ATTRIBUTIONS.md notices of derived code.

The glibc archives are linked against glibc 2.34 (cargo-zigbuild) and start on any Linux with glibc 2.34 or newer, such as Ubuntu 22.04, Debian 12 and RHEL 9. The static musl archives run on any Linux, glibc or musl, and are the choice for older systems such as RHEL 8, Debian 11, Ubuntu 20.04 or Amazon Linux 2. The Action, the pre-commit launcher and the Homebrew formula pick the musl archive themselves when the glibc is older than 2.34 or cannot be identified. cargo binstall cannot see the glibc version, so on Linux it always installs the static musl archive of the matching architecture (the crate’s binstall metadata redirects the -gnu targets to it); it runs on any glibc, including older than 2.34. For the glibc archive, download it from the release page. The npm addon targets glibc 2.17 and is not affected.

Verify a download with:

Terminal window
sha256sum --check --ignore-missing checksums.txt
- uses: actions/checkout@v7
- uses: polylint/skif@v0.8
with:
fail-on-warnings: true

See integrations for the inputs.

Terminal window
git clone https://github.com/polylint/skif
cd skif
cargo build --release

The binary is target/release/skif.

skif supports the versions of Node.js, Bun, Rust and the package managers its upstream still supports; where an upstream has no end-of-life policy, the latest two major versions. That is Node.js 22, 24 and 26, the newest Bun 1.x, the latest two majors of npm, pnpm and Yarn 2+, and the newest Yarn Classic 1.x.

Every change is tested end to end against workspaces that the real package manager installs: the newest release of each manager’s latest and previous major (for Bun and Yarn Classic, the newest 1.x) under every dependency layout it ships, on Linux, and the latest majors also on macOS and Windows.

Package manager Versions Layouts Operating systems
npm latest two majors hoisted Linux, macOS, Windows (previous major: Linux)
pnpm latest two majors isolated, nodeLinker: hoisted Linux, macOS, Windows (previous major: Linux)
Yarn 2+ latest two majors Plug’n’Play, nodeLinker: node-modules, nodeLinker: pnpm Linux, macOS, Windows (previous major: Linux)
Yarn Classic newest 1.x hoisted Linux, macOS, Windows
Bun newest 1.x default, linker = "hoisted", linker = "isolated" Linux, macOS, Windows

The scenarios cover a clean workspace, a set of fixable manifest and workspace issues fixed with --fix, catalogs (pnpm, Bun and Yarn 4.10 and later), -r over nested workspaces and a standalone package, JS analysis against the installed layout, skif baseline, skif migrate and toolchain pins (ADR 0015).

Older versions may work, but there is no guarantee: they are not tested, not blocked (engines is advisory), and bugs reproducible only on them are not fixed. A version is dropped in the first release after it reaches end-of-life (ADR 0015).