alerque/coreutils — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2025-05-31
Build shell scripts that run identically on Linux, macOS, and Windows without command-not-found errors.
Standardize command-line tools on Windows development machines that need to run scripts originally written for Linux.
Create cross-platform CI pipelines using a consistent set of core utilities.
Build only the specific command-line tools you need instead of the entire suite.
| alerque/coreutils | 0xr10t/pulsefi | 404-agent/codes-miner | |
|---|---|---|---|
| Stars | — | 0 | 0 |
| Language | Rust | Rust | Rust |
| Last pushed | 2025-05-31 | — | — |
| Maintenance | Stale | — | — |
| Setup difficulty | moderate | hard | moderate |
| Complexity | 4/5 | 4/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Rust toolchain installed and building from source, deploying as drop-in replacements requires setting up symlinks or binary aliases.
Every computer operating system ships with a set of basic command-line tools, things like ls (list files), cp (copy), rm (remove), cat (view file contents), and dozens more. On Linux, these come from a package called GNU coreutils. uutils coreutils is a from-scratch rebuild of that same toolkit, written in a programming language called Rust. The goal is to provide the exact same commands with the exact same behavior, so that scripts and workflows built around the GNU originals work as drop-in replacements without modification. The main motivation is portability. The GNU originals are tightly coupled to Unix-like systems, which means they don't run natively on Windows. Because Rust compiles to many platforms, this rewrite works on Linux, macOS, Windows, and others. That means someone writing a shell script or automation pipeline on a Mac can run the same commands on a Windows machine or a Linux server without hitting "command not found" errors or subtle behavioral differences. The project is built so that all the utilities compile into a single "multicall" binary, one executable file that behaves differently depending on the name used to call it, similar to how BusyBox works. You can also build only the specific tools you need rather than the whole suite. The README notes that while every program has been implemented, some options may still be missing or behave differently, and the project treats any deviation from GNU's behavior as a bug. The target audience is developers and system administrators who want a consistent set of command-line tools across different operating systems, for instance, someone building cross-platform CI pipelines, or a team standardizing on Windows development machines that still need to run scripts originally written for Linux. The project tracks its progress by measuring how many of the official GNU test suite's tests it passes, and the README shows that number has been climbing steadily over time.
A from-scratch rewrite of GNU coreutils (ls, cp, cat, etc.) in Rust that works as a drop-in replacement across Linux, macOS, and Windows for cross-platform command-line consistency.
Mainly Rust. The stack also includes Rust, Cargo.
Stale — no commits in 1-2 years (last push 2025-05-31).
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.