Scoop vs Yarn

Github repo can be found here.

Unlike some competitors, there is no free nor paid version, simply the FLOSS software as it is built.

Installing for all users requires admin permissions in order to be secure, so scoop installs without that requiring an elevated command prompt.

Packages have well-defined, simple names, without any unnecessary duplication, and are actively maintained. If you are used to Homebrew in OSX, you will (almost) feel at home.

Easy to upgrade installed packages, unlike in Chocolately which makes you pay for upgrade feature.

If the standard package selection isn't enough for you, you can easily find additional "buckets" that suit your needs. You can also create your own and share them.
See here.

In Chocolatey, if a package declares dependencies on a bad version of a package, installation or upgrade might break. Scoop dependencies are the latest version of a package, which reduces the chance of things breaking.

E.g. installing npm configures the global package prefix to your local app folder, and curl includes the Mozilla CA list.

Many installers leave behind a folder in your program files & program files (x86) folder. Since Scoop does not normally touch the folder, there is no problem of clogging it.

One of the most important aspects of Yarn is determinism (predictability). The lock file ensures that the same dependencies will always be installed in the same way and order regardless of the machine for a given repository.

yarn why <query> can tell you why a package was installed and what other packages depend on it.

Yarn efficiently queues up requests and avoids request waterfalls in order to maximize network utilization.

If you've installed a package before, you can install it again without any internet connection.

Resolve mismatching versions of dependencies to a single version to avoid creating duplicates.

Install any package from either npm or Bower and keep your package workflow the same.

A single request failing won't cause an install to fail. Requests are retried upon failure.

It looks like it has good documentation.

Even though it's still in its early stages of development, security is one of the core values on which Yarn is built. It uses checksums to verify the integrity of every package before executing its code. This also helps avoiding errors related to faulty caching or captive portals.

Further steps are also being taken to improve the security of Yarn which will be implemented in the future.

Even though it's backed by Facebook, Yarn is built as a community project first and foremost. It's completely open source and hosted on Github. It's released under a standard open source client and has its own GitHub organization and set up to work under the same governance model that other successful projects have used in the past, such as Rust and Ember.

All of this means that both existing and new contributors will always work together to improve the product and introduce new features while also keeping in mind suggestions coming from the community.

Was created in a collaboration of Facebook with Exponent, Google and Tilde.