[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-82944":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":16,"starSnapshotCount":16,"syncStatus":31,"lastSyncTime":32,"discoverSource":33},82944,"coreutils","microsoft\u002Fcoreutils","microsoft","Coreutils for Windows: Installer & Packaging","",null,"Rust",3910,64,23,33,0,80,1330,460,27.44,"MIT License",false,"main",true,[26,5,27],"command-line-tool","gnu-coreutils","2026-06-12 02:04:29","\u003Ch1 align=\"center\">Coreutils for Windows\u003C\u002Fh1>\n\n\u003Cp align=\"center\">UNIX-style core utilities for Windows. The same commands and pipelines you use on Linux, macOS, and WSL - natively.\u003C\u002Fp>\n\n\u003Ch3 align=\"center\">\n  \u003Ca href=\"#install\">Install\u003C\u002Fa>\n  \u003Cspan> · \u003C\u002Fspan>\n  \u003Ca href=\"#shell-conflicts\">Shell conflicts\u003C\u002Fa>\n  \u003Cspan> · \u003C\u002Fspan>\n  \u003Ca href=\"#windows-caveats\">Windows caveats\u003C\u002Fa>\n  \u003Cspan> · \u003C\u002Fspan>\n  \u003Ca href=\"#contributing\">Contributing\u003C\u002Fa>\n\u003C\u002Fh3>\n\n---\n\nA Microsoft-maintained build of [uutils\u002Fcoreutils](https:\u002F\u002Fgithub.com\u002Fuutils\u002Fcoreutils),\n[findutils](https:\u002F\u002Fgithub.com\u002Fuutils\u002Ffindutils), and [grep](https:\u002F\u002Fgithub.com\u002Fuutils\u002Fgrep) packaged as a\nsingle multi-call binary for Windows. The goal is to make moving between Linux, macOS, WSL,\ncontainers, and Windows frictionless: the same commands, flags, and pipelines work the same\nway, so existing scripts carry over without translation.\n\nEach command supports the standard `--help` flag for full syntax and options.\n\n**This project is in preview.**\n\n\u003Cbr\u002F>\n\n## Install\n\nInstall Coreutils for Windows with WinGet:\n\n```powershell\nwinget install Microsoft.Coreutils\n```\n\nOr grab the latest build from our [Release Page](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcoreutils\u002Freleases\u002Flatest).\n\n\u003Cbr\u002F>\n\n## Shell conflicts\n\n> [!NOTE]\n> Any command not mentioned is included in this suite. The following only lists conflicts.\n\n> [!WARNING]\n> PowerShell 7.4 or newer is required. Older PowerShell versions aren't supported.\n\nSeveral commands share names with built-ins in CMD and PowerShell. Whether the Coreutils\nversion runs depends on the shell, the PATH order, and (for PowerShell) the alias table.\n\nLegend: ✅ ships and works · ⚠️ ships but conflicts with a built-in · 🛑 not shipped\n\n| Command    | CMD  | PowerShell 7.4+ | Notes |\n| ---------- | :--: | :-------------: | ----- |\n| `cat`      |  ✅  |       ⚠️        | |\n| `cp`       |  ✅  |       ⚠️        | |\n| `date`     |  ⚠️  |       ⚠️        | |\n| `dir`      |  🛑  |       🛑        | Conflicts with the built-in DOS command |\n| `echo`     |  ⚠️  |       ⚠️        | |\n| `expand`   |  🛑  |       🛑        | Conflicts with the built-in DOS command |\n| `find`     |  ✅  |       ✅        | Integrated port of the original DOS command |\n| `hostname` |  ✅  |       ✅        | Superset of the Windows built-in |\n| `kill`     |  🛑  |       🛑        | Unavailable due to lack of signals on Windows; Implementing a form of SIGTERM\u002FSIGKILL may be possible in the future however |\n| `ls`       |  ✅  |       ⚠️        | |\n| `mkdir`    |  ⚠️  |       ⚠️        | |\n| `more`     |  🛑  |       🛑        | Conflicts with the built-in DOS command (consider `edit` as an alternative) |\n| `mv`       |  ✅  |       ⚠️        | |\n| `pwd`      |  ✅  |       ⚠️        | |\n| `rm`       |  ✅  |       ⚠️        | |\n| `rmdir`    |  ⚠️  |       ⚠️        | |\n| `sleep`    |  ✅  |       ⚠️        | |\n| `sort`     |  ✅  |       ⚠️        | Integrated port of the original DOS command |\n| `tee`      |  ✅  |       ⚠️        | |\n| `timeout`  |  🛑  |       🛑        | Relies on `kill`'s functionality |\n| `uptime`   |  ✅  |       ⚠️        | |\n| `whoami`   |  🛑  |       🛑        | Conflicts with the built-in Windows command |\n\n\u003Cbr\u002F>\n\n## Windows caveats\n\n| Difference            | Detail |\n| --------------------- | ------ |\n| **CRLF line endings** | Windows text files often use CRLF (`\\r\\n`). Most utilities handle this transparently, but pattern matching with `$` and exact byte counts can be affected. |\n| **No `\u002Fdev\u002Fnull`**    | Use `NUL` instead, for example `find . -name \"*.log\" > NUL` |\n| **No POSIX signals**  | Signals such as `SIGHUP`, `SIGPIPE`, and `SIGUSR` aren't available. `Ctrl+C` (`SIGINT`) works as expected. |\n| **Path separators**   | Both `\u002F` and `\\` are accepted. Some utilities produce `\\`-separated output, which can affect downstream piping. |\n| **File permissions**  | Windows uses ACLs, not POSIX permission bits. Permission-based predicates (for example `find -perm`) may behave differently or be unavailable. |\n| **Symbolic links**    | Reading existing symbolic links works without elevation. Creating new symbolic links requires Developer Mode ([**Settings > System > Advanced**](https:\u002F\u002Flearn.microsoft.com\u002Fwindows\u002Fadvanced-settings)) or an elevated terminal. |\n\n### PowerShell Command Parsing\n\nThe installer integrates itself with interactive PowerShell sessions via `PSReadLine`.\nIt ensures that quoted expression behave somewhat like they do under UNIX shells or CMD:\n`echo *.txt` will then print a number of file names, while `echo '*.txt'` will print \"*.txt\" literally.\n\nThere are two shortcomings, however:\n* PowerShell's escape character is still \u003Ccode>\\`\u003C\u002Fcode>, not \u003Ccode>\\\\\u003C\u002Fcode>\u003Cbr>\n  While you may write `find . \\( -foo -bar \\)` with Bash, you still need to write ``find . `( -foo -bar `)`` in PowerShell.\n* `Get-Command ls`, `Get-Help ls`, etc., will still show `ls`, etc., as builtin commands\u003Cbr>\n  Due to limitations around `PSNativeCommandPreserveBytePipe` we cannot integrate ourselves in a more robust way with PowerShell.\n\n### Intentionally dropped\n\nCommands that exist upstream but aren't shipped here because they rely on POSIX-only concepts, would break existing Windows scripts, or simply aren't useful on Windows.\n\n* `dd`: Perhaps useful in the future.\n* `dircolors`, `shred`, `sync`, `uname`: Not particularly useful on Windows.\n* `chcon`, `chgrp`, `chmod`, `chown`, `chroot`, `groups`, `hostid`, `id`, `install`,\n  `logname`, `mkfifo`, `mknod`, `nice`, `nohup`, `pathchk`, `pinky`, `runcon`, `stdbuf`,\n  `stty`, `tty`, `users`, `who`: POSIX-only concepts unavailable on Windows.\n\n\u003Cbr\u002F>\n\n## Contributing\n\nBug reports and pull requests are welcome. See [`CONTRIBUTING.md`](.\u002FCONTRIBUTING.md) for details on the repo layout and how changes flow between this repo and the upstream uutils projects.\n","Coreutils for Windows 是一个为 Windows 平台提供类 UNIX 核心工具的项目。它将 uutils\u002Fcoreutils、findutils 和 grep 打包成一个适用于 Windows 的多调用二进制文件，旨在让用户在 Linux、macOS、WSL 以及 Windows 之间无缝切换，保持命令、标志和管道的一致性。该项目使用 Rust 语言编写，确保了高性能与内存安全。适合需要跨平台一致性的开发者或系统管理员使用，在日常脚本编写及执行中能够极大提升效率。注意，由于与 CMD 或 PowerShell 中的部分内置命令存在命名冲突，用户需根据具体环境调整 PATH 顺序或别名设置来正确调用这些工具。",2,"2026-06-11 04:09:40","CREATED_QUERY"]