ScoopInstaller/Main: The Default Bucket That Defines Scoop's Package Universe
The default bucket for Scoop. This is the default bucket for Scoop and is added by default.
At a glance
- What is it?
- ScoopInstaller/Main is the core manifest repository for the Scoop Windows package manager. It is the default bucket, added on install, and its criteria for inclusion shape what most Scoop users can install.
- Who is it for?
- Adopt ScoopInstaller/Main if you are a Scoop user who wants the curated, vetted set of core applications that the Scoop project maintains. It is the right default for most desktop users and developers on Windows who want command-line installation without admin rights.
- Can I use it commercially?
- Yes. Unlicense is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly PowerShell, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What This Repository Actually Is
ScoopInstaller/Main is not a program you run. It is a collection of manifest files, written in PowerShell, that describe how to install software on Windows through Scoop. The README calls it the default bucket for Scoop, meaning it is added automatically when you install Scoop itself. If you have Scoop, you already have access to this bucket. The repository is the reason a command like `scoop install git` works out of the box. It is the front door to Scoop's package ecosystem. Without it, Scoop would be an installer with nothing to install.
The Problem It Solves: Curated Windows Installation
Windows lacks a native package manager that works across the command line and respects user-level installs. Scoop fills that gap, and Main provides the initial set of packages. The problem it solves is twofold. First, it gives users a trusted source of manifests, so they do not have to hunt for download links or write their own installation scripts. Second, it enforces a set of criteria for what can be included, which the README links to as the Main criteria. That means the bucket is not a free-for-all. It is a filtered list, and that filtering is the value. For engineers who want a reproducible way to set up a Windows machine, Main is the starting point.
How the Bucket Works: Manifests and the Default Addition
The mechanism is simple: each manifest is a file that describes a piece of software, including where to download it, how to extract it, and what shims to create. When you run `scoop install <manifest>`, Scoop reads the manifest from the bucket and executes the steps. The README states that this is the default bucket and is added by default. That means the installation of Scoop itself wires up Main, so no extra configuration is needed. The repository also contains references to two GitHub Actions workflows, `ci.yml` and `excavator.yml`. The `ci.yml` likely runs checks on the manifests, and `excavator.yml` is the automated bot that updates manifests when upstream versions change. That automation is what keeps the bucket fresh, though the README does not detail the exact process.
Getting Started: Installing Manifests and Contributing
To use the bucket, you first need Scoop installed. Once Scoop is present, the README says you simply run `scoop install <manifest>`. For example, `scoop install git` would install Git, assuming that manifest exists in Main. There is no separate step to add the bucket, because it is the default. If you want to add a new manifest to the repository, the README points to a Contributing Guide. That guide lives in a separate repository, `ScoopInstaller/.github`, and it is the required reading before making a contribution. The README does not give the full contribution process, but it makes clear that you must read that guide first. That is the entire setup: install Scoop, use the manifests, and follow the guide if you want to add to the collection.
Limitations: What Main Does Not Include
The biggest limitation is the Main criteria itself. The README links to the criteria for including apps, which means not every piece of software is eligible. Based on what Scoop's criteria typically are, Main excludes commercial or non-free software, apps that require admin rights to install, and often GUI-only applications that do not fit the command-line philosophy. That is a real constraint. If you need a proprietary tool like Discord or a heavy IDE like Visual Studio, Main is not where you will find them. You would need to use a different bucket, such as the Extras bucket, which is not covered in the README. Another limitation is that the bucket is only as good as its automation. If the excavator bot fails or a manifest is not updated, you may get an older version. The README does not promise any manual review beyond the CI checks.
Alternatives: Comparing with Other Buckets
The obvious alternative is the Scoop Extras bucket, which is a separate repository that hosts manifests for apps that do not meet the Main criteria. The difference in approach is that Extras is less restrictive. It includes GUI apps and some non-free software, but it is not the default bucket, so you have to add it manually with `scoop bucket add extras`. That is a real difference: Main is curated for core, command-line-friendly tools, while Extras is a broader collection. Another alternative is using Scoop itself with a custom bucket that you write yourself. That gives you full control but requires you to maintain your own manifest files. The README does not mention these alternatives, but they are the logical next step for anyone who hits the limits of Main. The choice comes down to whether you want the curated default or the wider net.
Maintenance, Upgrades, and License
The repository is actively maintained, as indicated by the CI and excavator workflows referenced in the README. The last push date is unknown, and there are no recent releases listed, but that is typical for a manifest repository, which does not need versioned releases. The license is Unlicense, which means the manifests are in the public domain. That is a permissive license, so you can reuse the manifest files for your own purposes without restriction, though it is not legal advice. The maintenance cost for a user is low: you do nothing, because the bucket is updated automatically when Scoop refreshes. For a contributor, the cost is higher, because you must follow the Contributing Guide and ensure your manifest meets the criteria. The README does not specify how often the bucket updates, but the presence of the excavator bot suggests it is frequent.
Editorial conclusion
Adopt ScoopInstaller/Main if you are a Scoop user who wants the curated, vetted set of core applications that the Scoop project maintains. It is the right default for most desktop users and developers on Windows who want command-line installation without admin rights. Do not use it if you need niche, GUI-heavy, or non-free software, because the Main criteria exclude those. Before relying on it, check the criteria for inclusion and the Contributing Guide to understand what is inside and how it changes. Verify the current state of the repository and its CI status, since the README references automated workflows that keep manifests updated.
Community notes