dorado is a Scoop bucket — a community-maintained set of Windows application manifests — for developers who want command-line toolchains installed on their own user account without administrator rights.

What it is

dorado lives in the Scoop ecosystem, the package manager for Windows that installs applications into a user's home directory instead of system-wide Program Files. A Scoop bucket is a Git repository of JSON app manifests, and dorado is one such bucket, maintained by chawyehsu under the PowerShell/Scoop tooling family alongside the official buckets.

The concrete problem it solves is elevation. C and C++ toolchains, version managers, and runtimes on Windows traditionally arrive as installers that demand an administrator prompt and write to machine-wide paths. Every manifest in dorado avoids that: none of the apps require elevated privileges to install. It replaces the per-app manual download, elevated installer, and hand-edited PATH routine with a single scoop install command, and it also replaces the official-bucket route for a small set of manifests that deliberately differ — for example an nvm-windows fork stripped of the elevated permission requirement, and a Miniconda3 variant that keeps the default environment out of PATH until it is activated.

Key capabilities

• Ships manifests for mingw-w64 toolchains: llvm-mingw (LLVM/Clang/LLD based), winlibs-mingw-msvcrt, winlibs-mingw-ucrt, winlibs-mingw-llvm-ucrt, and the minimalist nuwen-mingw-gcc, which provides only gcc and ld with no make or gdb.
• Provides nvm-windows, a fork that removes the elevated permission requirement so non-admin Scoop users can manage Node versions.
• Provides rustup-np, the non-portable Rustup variant that keeps .rustup and .cargo in their original location under $env:USERPROFILE.
• Provides volta, positioned in the README as a replacement for nvm-windows.
• Provides miniconda3 without polluting PATH: the base environment is added only after conda activate base.
• Provides trash, which moves files and folders to the recycle bin instead of forcing users to reach for rm -rf.
• Keeps the whole bucket non-administrative, so installs land in the user profile and need no UAC prompt.

Who uses it and how

• Developers on locked-down corporate Windows machines with no administrator rights, who need Node or C toolchains and cannot run an elevated installer.
• C and C++ developers who want to switch between MSVCRT, UCRT, and LLVM-based mingw-w64 builds without managing separate downloads by hand.
• Rust and Node users who want version managers confined to $env:USERPROFILE rather than scattered across machine-level locations.
• Contributors filing new app requests through the repository's GitHub issue tracker, and contributors who fork the bucket, update an outdated manifest, and open a pull request. The README directs new manifests to the official buckets first when they meet the official criteria, so dorado acts partly as a staging and holding area.
• The repository carries roughly 1,200 stars and 111 forks, with around 40 open issues, which indicates a modest, hobby-scale contribution base rather than a staffed distribution team.

Getting started

Install Scoop first, then run scoop bucket add dorado https://github.com/chawyehsu/dorado in PowerShell, and install any app with scoop install dorado/. There is no separate installer, hosted service, or container image — the Git repository is the distribution channel.

How it compares

dorado sits at Scoop's bucket layer, next to the official buckets that the README asks contributors to prefer when a new manifest qualifies for them. No comparable bucket or package registry is named in the available facts, so within this registry it stands alone.

When to use it — and when not to

A self-hoster operates nothing beyond Scoop itself: there is no database, object store, or SMTP service to run, and installations are per-user file drops. The honest limitations are documentation and maintenance shape. The README is short and covers only a featured-app table plus a short question-and-answer section, offering no release process, versioning scheme, or support policy; updates depend on someone noticing an outdated manifest and filing a pull request, and the README explicitly asks would-be requesters to try the official buckets first, so coverage here is narrow by design. Anyone needing a contractual support channel, an audited release cadence, or an app outside the featured set should look to the official buckets rather than this one, and organisations with strict licence review should note the Unlicense terms before adopting.

scoop bucket add dorado https://github.com/chawyehsu/dorado

scoop install dorado/<app_name>