About CommandLine Directory
Verified one-command installs for developer tools.
What we do
Developer tools usually document installation in one place — a README, an install script — and finding that one line usually means searching a search engine, opening three tabs, and reading past a security advisory. We collect the install command itself and show it, per operating system, on one page.
For every tool listed we record the install command verbatim, along with where it came from. Roughly 217 of the 244 commands we publish were checked directly against the project's own README on GitHub. The rest come from the project's public source.
What we don't do
- We don't invent commands. If a project doesn't document a macOS install, the macOS tab says so and links to the project. It never substitutes a different command or a command we made up.
- We don't host installers. Every command points at the project's own server or repository. Nothing is proxied through us.
- We don't sell anything. No "PRO" edition, no upsell, no paid tier. The tools listed are free and open source and remain so.
- We don't track you. See the privacy policy.
Independence and trademarks
CommandLine Directory is an independent reference. We are not affiliated with, endorsed by, sponsored by, or operated by any of the projects listed. Product and project names are the trademarks of their respective owners and are used only to identify what a page is about.
Safety
Some commands fetch a script from the internet and run it. That is what the projects
document, and it is a normal way to install software — but it means the script can change
between the day we recorded the command and the day you run it. Where this is the case we
label it. Read scripts you don't recognise, and prefer a package manager
(winget, brew, scoop, cargo) when the
project offers one — package managers are generally easier to audit and easier to undo.
Corrections
If a command here is wrong, out of date, or mislabelled, we'd like to fix it. See contact.