Yarn Alternatives

We're npm, Inc., the company behind Node package manager, the npm Registry, and npm CLI. We offer those to the community for free, but our day job is building and selling useful tools for developers like you. Get started today for free, or step up to npm Pro to enjoy a premium JavaScript development experience, with features like private packages. Bring the best of open source to you, your team, and your company. Relied upon by more than 11 million developers worldwide, npm is committed to making JavaScript development elegant, productive, and safe. The free npm Registry has become the center of JavaScript code sharing, and with more than one million packages, the largest software registry in the world. Our other tools and services take the Registry, and the work you do around it, to the next level. At npm, Inc., we're proud to dedicate teams of full-time employees to operating the npm Registry, enhancing the CLI, improving JavaScript security, and other projects.

Chocolatey has the largest online registry of Windows packages. Chocolatey packages encapsulate everything required to manage a particular piece of software into one deployment artifact by wrapping installers, executables, zips, and/or scripts into a compiled package file. Package submissions go through a rigorous moderation review process, including automatic virus scanning. The community repository has a strict policy on malicious and pirated software. Many organizations face the ongoing challenge of deploying and supporting various versions of software. Chocolatey allows organizations to automate and simplify the management of their complex Windows environments. Our customers have experienced a massive reduction in effort, improved speed of deployment, high reliability, and comprehensive reporting. Reduce complexity, save yourself time, and get up to speed on the latest technologies and approaches.

Packagist is the main composer repository. It aggregates public PHP packages installable with Composer. Put a file named composer.json at the root of your project, containing your project dependencies. Packagist is the default Composer package repository. It lets you find packages and lets Composer know where to get the code from. You can use Composer to manage your project or libraries' dependencies. First of all, you must pick a package name. This is a very important step since it can not change and it should be unique enough to avoid conflicts in the future. The package name consists of a vendor name and a project name joined by a/. The vendor name exists to prevent naming conflicts. The composer.json file should reside at the top of your package's git/svn/ repository and is the way you describe your package to both packagist and composer. New versions of your package are automatically fetched from tags you create in your VCS repository.

Aptitude is an Ncurses and command-line based front-end to numerous Apt libraries, which are also used by Apt, the default Debian package manager. Aptitude is text-based and run from a terminal. A mutt-like syntax for matching packages in a flexible manner. Mark packages as "automatically installed" or "manually installed" so that packages can be auto-removed when no longer required (feature available in Apt, too, since quite a few Debian releases). Preview of actions about to be taken with different colors marking different actions. The ability to interactively retrieve and display the Debian changelog of all available official packages. Score-based dependency resolver which is more suitable for interactive dependency resolution with additional hints from the user like "I don't want that part of the solution but keep that other part of the solution for your next try". Apt's dependency resolver on the other hand is optimized for good "one-shot" solutions.

Nix is a tool that takes a unique approach to package management and system configuration. Learn how to make reproducible, declarative, and reliable systems. Nix builds packages in isolation from each other. This ensures that they are reproducible and don't have undeclared dependencies, so if a package works on one machine, it will also work on another. Nix makes it trivial to share development and build environments for your projects, regardless of what programming languages and tools you’re using. Nix ensures that installing or upgrading one package cannot break other packages. It allows you to roll back to previous versions and ensures that no package is in an inconsistent state during an upgrade. Nix is a purely functional package manager. This means that it treats packages like values in purely functional programming languages such as Haskell, they are built by functions that don’t have side effects, and they never change after they have been built.

Web sites are made of lots of things, frameworks, libraries, assets, and utilities. Bower manages all these things for you. Keeping track of all these packages and making sure they are up to date (or set to the specific versions you need) is tricky. Bower to the rescue! Bower can manage components that contain HTML, CSS, JavaScript, fonts, or even image files. Bower doesn’t concatenate or minify code or do anything else, it just installs the right versions of the packages you need and their dependencies. To get started, Bower works by fetching and installing packages from all over, taking care of hunting, finding, downloading, and saving the stuff you’re looking for. Bower keeps track of these packages in a manifest file, bower.json. How you use packages is up to you. Bower provides hooks to facilitate using packages in your tools and workflows. Bower is optimized for the front-end. If multiple packages depend on a package, jQuery, for example, Bower will download jQuery just once.

Fast, reliable, and secure software starts here. A unified, developer-friendly interface for all of your artifacts written in any language, delivered to any infrastructure. Ship securely and quickly knowing your packages are handled by packagecloud. Consistent package repositories, at enterprise scale and startup speed. A single API and CLI for every environment and package type. Works seamlessly and harmoniously with the systems you already use. Manage all of your packages and deploy to any environment, from one beautiful interface, on-premise or in the cloud. Packagecloud supports the most popular package types, from Java to Python to Ruby and Node, and more. Built for teams with collaboration and access control features. Packagecloud just works. Upload any supported package type via a single, consistent API and deploy with ease. We run thousands of tests to ensure correct and consistent behavior even in the face of bugs in the packaging systems themselves.

Gemfury is a hosted repository for your public and private packages, where they are safe and within reach. Install them to any machine in minutes without worrying about running and securing your own repository server. Gemfury works with RubyGems, Python packages, npm modules, and all compatible frameworks and services. Authenticated Repo-URL keeps your private packages safe and secure during deployment. All management and deployment is done over SSL. Do everything you need with just a few terminal commands. We are hackers and love the command line; this one is our favorite. Gemfury is designed for teams. Share your account with coworkers and let them easily access your packages. Gemfury works with RubyGems, Python packages, npm modules, and all compatible frameworks and services. Install and use your code anywhere. Seamless integration and secure installation. Collaborate with your team.

Protect your software supply chain with the ActiveState Platform. The only turn-key software supply chain that automates and secures importing, building & consuming open source. Available now for Python, Perl & Tcl. Our secure supply chain starts with modern package management that’s 100% compatible with the packages you use, highly-automated, and includes key enterprise features. Automated builds from source code, including linked C libraries. Per-package and per-version vulnerability flagging ensures you can automatically build/rebuild secure environments. A complete Bill of Materials (BOM) including provenance, licensing & all dependencies, including transient, OS & shared dependencies. Built-in virtual environments simplify development, debugging, testing and multi-project work. Web UI, API & CLI for Windows/Linux, with full macOS support soon. Spend less time wrestling with packages, dependencies, and vulnerabilities and more time focused on doing what you do best, coding!

MSYS2 is a collection of tools and libraries providing you with an easy-to-use environment for building, installing and running native Windows software. It consists of a command line terminal called mintty, bash, version control systems like git and subversion, tools like tar and awk and even build systems like autotools, all based on a modified version of Cygwin. Despite some of these central parts being based on Cygwin, the main focus of MSYS2 is to provide a build environment for native Windows software and the Cygwin-using parts are kept at a minimum. MSYS2 provides up-to-date native builds for GCC, mingw-w64, CPython, CMake, Meson, OpenSSL, FFmpeg, Rust, Ruby, just to name a few. To provide easy installation of packages and a way to keep them updated it features a package management system called Pacman, which should be familiar to Arch Linux users.

AppGet is a Github moderated, open source package manager which focuses on security, automation and ease-of-use. All moderation is done in GitHub. Anyone can submit a pull request which is then checked and approved by our team. Install, update and remove any application available in our library even if the application wasn’t originally installed with AppGet. Our client code and application library are completely open source and available on GitHub. AppGet bots work around the clock to ensure our application library is kept up-to-date with the latest versions. Applications in AppGet's library are always downloaded directly from the author. No more looking around the web looking for the download link. AppGet uses metadata-only manifest files. This makes reviewing manifest much simpler and generally much more secure.

DNF is a software package manager that installs, updates, and removes packages on Fedora and is the successor to YUM (Yellow-Dog Updater Modified). DNF makes it easy to maintain packages by automatically checking for dependencies and determining the actions required to install packages. This method eliminates the need to manually install or update the package, and its dependencies, using the rpm command. DNF is now the default software package management tool in Fedora. Removes packages installed as dependencies that are no longer required by currently installed programs. Checks for updates, but does not download or install the packages. Provides basic information about the package including name, version, release, and description.

If you are new to the Windows Package Manager, you might want to Explore the Windows Package Manager tool. The packages available to the client are in the Windows Package Manager Community Repository. The client requires Windows 10 1809 (build 17763) or later at this time. Windows Server 2019 is not supported as the Microsoft Store is not available nor are updated dependencies. It may be possible to install on Windows Server 2022, this should be considered experimental (not supported), and requires dependencies to be manually installed as well.

Package manager and build system for Fortran. There are already many packages available for use with fpm, providing an easily accessible and rich ecosystem of general-purpose and high-performance code. Fortran Package Manager (fpm) is a package manager and build system for Fortran. Its key goal is to improve the user experience of Fortran programmers. It does so by making it easier to build your Fortran program or library, run the executables, tests, and examples, and distribute it as a dependency to other Fortran projects. Fpm’s user interface is modeled after Rust’s Cargo. Its long-term vision is to nurture and grow the ecosystem of modern Fortran applications and libraries. The Fortran package manager has a plugin system that allows it to easily extend its functionality. The fpm-search project is a plugin to query the package registry. Since it is built with fpm we can easily install it on our system.

With GitHub Packages, you can safely publish and consume packages within your organization or with the entire world. Use industry and community-standard package managers with native tooling commands. Then authenticate and publish directly to GitHub. Understand and safely install package contents. Get packages directly from the community on GitHub, and use only what’s been approved for your organization. Store your packages in the same secure environment as your source code, all protected by your GitHub credentials. With a full API and webhooks support, you can extend your workflows to work with GitHub Packages. GitHub Packages is built with the latest edge caching via a global CDN to deliver great performance, no matter where your builds run. Use Actions to automatically publish new package versions to GitHub Packages. Run your CI/CD with Actions, and install packages and images hosted on GitHub Packages or your preferred registry of record.

The Portage Development Project works to provide a continuously expanding and developing tool for the management and installation of packages. The developers work on providing a coherent system that is as trouble free as possible (backwards compatible, automated, and simple). Bugs are tracked and fixed from the Gentoo bug tracker and developer-developer correspondence is maintained on the gentoo-portage-dev mailing list. Another communication channel is the #gentoo-portage (webchat) IRC channel on the Libera.Chat network. The goal of the Portage project is to provide a seamless integration of developer and user tools to aid the growth and maintenance of Gentoo packages. This means we work not only on Portage itself, but also on associated tools, and on ensuring that our APIs are useful to other tools.

Introducing tea - the revolutionary, cross-platform package manager. Say goodbye to slow & clunky, and say hello to fast & smooth. From the creator of Brew. With tea, simply type commands and it takes care of the rest. Get the latest versions of open source tools and support specific tool versions for different projects. Experience better package management with tea. And through that packaging infrastructure, we have plans of leveraging blockchain to help remunerate devs for their contributions to OSS. You can learn more about our grand ambitions for web3 by checking out our white paper here. Easily access the entire open source ecosystem with tea. Simply prefix your commands with "tea" and if the tool isn't installed, tea will install it for you. Add magic to your shell scripts and use developer environments to enhance your workflow. magic is optional; if you don’t enable it, then just prefix your commands with `tea`.

The Fink project wants to bring the full world of Unix open source software to Darwin and Mac OS X. We modify Unix software so that it compiles and runs on Mac OS X ("port" it) and make it available for download as a coherent distribution. Fink uses Debian tools like dpkg and apt-get to provide powerful binary package management. You can choose whether you want to download precompiled binary packages or build everything from source. The project offers precompiled binary packages as well as a fully automated build-from-source system. Mac OS X includes only a basic set of command-line tools. Fink brings you enhancements for these tools as well as a selection of graphical applications developed for Linux and other Unix variants. With Fink the compile process is fully automated; you'll never have to worry about Makefiles or configure scripts and their parameters again. The dependency system automatically takes care that all required libraries are present.

Rails Assets is the frictionless proxy between Bundler and Bower. It automatically converts the packaged components into gems that are easily droppable into your asset pipeline and stay up to date. First, make sure you use bundler >= 1.8.4. Add Rails Assets as a new gem source, then reference any Bower components that you need as gems. In development, if you have issues with SSL certificates and security is not a priority, you can use the alternate endpoint instead. During bundle install, if Bundler requests a package like this, Rails Assets’ daemon automatically will fetch the component from Bower’s registry, analyze its manifest file, bower.json, repackage the component as a valid Ruby gem and serve it to your application. Dependencies are handled the same way recursively. Gems created by Rails Assets work great with any Sprockets-based application. It works with Sinatra too!

Don’t risk an installation error and poor customer experience. InstallAnywhere is the leading multi-platform solution for developers creating installers for physical, virtual, and cloud environments. InstallAnywhere makes it easy for developers to create professional installation software that performs the same, no matter what the platform. You’ll be able to create reliable installations for on-premises platforms like Windows, Linux, Apple, Solaris, AIX, HP-UX, and IBM, and then deploy them physically, virtually, or to the cloud (you can even package it up into a Docker container) all from a single project file. Whether for standalone instances or integrated into your current systems, with InstallAnywhere, you’ll be able to adapt to industry changes quickly, get to market faster and deliver an engaging customer experience. Reduce software development time and go to market faster. Impress end-users with customized installations. Simplify Virtualization and cloud-based deployments.

Apache Ivy™ is a popular dependency manager focusing on flexibility and simplicity. Find out more about its unique enterprise features, what people say about it, and how it can improve your build system! Ivy is a tool for managing (recording, tracking, resolving, and reporting) project dependencies. Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead, it provides the necessary flexibility and reconfigurability to be adapted to a broad range of dependency management and build processes. While available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. Ivy has a lot of powerful features, the most popular and useful being its flexibility, integration with Ant, and strong transitive dependencies management engine. Ivy is open source and released under a very permissive Apache License.

Pacman is a utility which manages software packages in Linux. It uses simple compressed files as a package format, and maintains a text-based package database (more of a hierarchy), just in case some hand tweaking is necessary. Pacman does not strive to "do everything." It will add, remove and upgrade packages in the system, and it will allow you to query the package database for installed packages, files and owners. It also attempts to handle dependencies automatically and can download packages from a remote server. Version 2.0 of Pacman introduced the ability to sync packages (the - sync option) with a master server through the use of package databases. Prior to this, packages would have to be installed manually using the --add and - upgrade operations.

Installing, patching, and removing software packages on Linux machines is one of the common tasks every sysadmin has to do. Here is how to get started with Linux package management in Linux Red Hat-based distributions (distros). Package management is a method of installing, updating, removing, and keeping track of software updates from specific repositories (repos) in the Linux system. Linux distros often use different package management tools. Red Hat-based distros use RPM (RPM Package Manager) and YUM/DNF (Yellow Dog Updater, Modified/Dandified YUM). YUM is the primary package management tool for installing, updating, removing and managing software packages in Red Hat Enterprise Linux. YUM performs dependency resolution when installing, updating, and removing software packages. YUM can manage packages from installed repositories in the system or from .rpm packages. There are many options and commands available to use with YUM.

Package, dependency, and environment management for any language, Python, R, Ruby, Lua, Scala, Java, JavaScript, C/ C++, Fortran, and more. Conda is an open-source package management system and environment management system that runs on Windows, macOS, Linux, and z/OS. Conda quickly installs, runs, and updates packages and their dependencies. Conda easily creates, saves, loads, and switches between environments on your local computer. It was created for Python programs, but it can package and distribute software for any language. Conda as a package manager helps you find and install packages. If you need a package that requires a different version of Python, you do not need to switch to a different environment manager, because conda is also an environment manager. With just a few commands, you can set up a totally separate environment to run that different version of Python, while continuing to run your usual version of Python in your normal environment.

Cargo is the Rust package manager. Cargo downloads your Rust package's dependencies, compiles your packages, makes distributable packages, and uploads them to crates.io, the Rust community’s package registry. You can contribute to this book on GitHub. To get started with Cargo, install Cargo (and Rust) and set up your first crate. The commands will let you interact with Cargo using its command-line interface. A Rust crate is either a library or an executable program, referred to as either a library crate or a binary crate, respectively. Loosely, the term crate may refer to either the source code of the target or to the compiled artifact that the target produces. It may also refer to a compressed package fetched from a registry. Your crates can depend on other libraries from crates.io or other registries, git repositories, or subdirectories on your local file system. You can also temporarily override the location of a dependency.

The RPM Package Manager (RPM) is a powerful package management system capable of building computer software from the source into easily distributable packages; installing, updating, and uninstalling packaged software; querying detailed information about the packaged software, whether installed or not; and verifying the integrity of packaged software and resulting software installation. The package’s metadata is stored in the RPM header. The header is a binary data structure that stores single pieces of data in tags. Each tag has a pre-defined meaning and data type. These are not stored in the header itself but need to be known by the code reading the header. In the header, the tags are only referred to by their number. Each tag is either of a plain scalar type or is an array of one of these types. While not enforced by the type system the RPM code assumes that tags belonging together have the same number of entries.

NuGet is the package manager for .NET. The NuGet client tools provide the ability to produce and consume packages. The NuGet Gallery is the central package repository used by all package authors and consumers. New to NuGet? Start with a walkthrough showing how NuGet powers your .NET development. Browse the thousands of packages that developers like you have created and shared with the .NET community. Want to make your first NuGet package and share it with the community? Start with our walkthrough! The command-line tool, nuget.exe, builds and runs under Mono 3.2+ and can create packages in Mono. Although nuget.exe works fully on Windows, there are known issues with Linux and OS X. The primary source for learning about a package is its listing page on NuGet (or another private feed). Each package page on NuGet includes a description of the package, its version history, and usage statistics.

The MacPorts Project is an open-source community initiative to design an easy-to-use system for compiling, installing, and upgrading either command-line, X11, or Aqua-based open-source software on the Mac operating system. To that end, we provide the command-line driven MacPorts software package under a 3-Clause BSD License, and through it easy access to thousands of ports that greatly simplify the task of compiling and installing open-source software on your Mac. We provide a single software tree that attempts to track the latest release of every software title (port) we distribute, without splitting them into “stable” vs. “unstable” branches, targeting mainly macOS Mojave v10.14 and later (including macOS Monterey v12 on both Intel and Apple Silicon). There are thousands of ports in our tree, distributed among different categories, and more are being added on a regular basis.

The missing package manager for macOS (or Linux). The script explains what it will do and then pauses before it does it. Homebrew installs the stuff you need that Apple (or your Linux system) didn’t. Homebrew installs packages to their own directory and then symlinks their files into /usr/local (on macOS Intel). Homebrew won’t install files outside its prefix and you can place a Homebrew installation wherever you like. Trivially create your own Homebrew packages. It’s all Git and Ruby underneath, so hack away with the knowledge that you can easily revert your modifications and merge upstream updates. Homebrew formulae are simple Ruby scripts. Homebrew complements macOS (or your Linux system). Install your RubyGems with gem and their dependencies with brew. Homebrew Cask installs macOS apps, fonts and plugins and other non-open source software. Making a cask is as simple as creating a formula.

Npackd (pronounced "unpacked") is a GPLv3 licensed installer/application store/package manager/marketplace for applications for Windows. It helps you to find and install software, keep your system up-to-date and uninstall it if no longer necessary. The process of installing and uninstalling applications is completely automated (silent or unattended installation and un-installation). It helps you to find and install software, keep your system up-to-date and uninstall it if no longer necessary. You can watch this short video to better understand how it works. The process of installing and uninstalling applications is completely automated (silent or unattended installation and un-installation).

Rudix is a build system target on macOS (formerly known as Mac OS X) with minor support to OpenBSD, FreeBSD, NetBSD, and Linux. The build system (also called "ports") provides step-by-step instructions for building third-party software, entirely from source code. Rudix provides more than a pure ports framework, it comes with packages, and precompiled software bundled up in a nice format (files *.pkg) for easy installation on your Mac. If you want to collaborate on the project, visit us at GitHub/rudix-mac or at our mirror at GitLab/rudix. Use the GitHub issue tracker to submit bugs or request features. Similar projects or alternatives to Rudix are Fink, MacPorts, pkgsrc, and Homebrew. Packages are compiled and tested on macOS Big Sur (Version 11, Intel only!), Catalina (Version 10.15) and OS X El Capitan (Version 10.11). Every package is self-contained and has everything it needs to work. The binaries, libraries, and documentation will be installed under /usr/local/.

Zypper is a command-line package manager for installing, updating, and removing packages. It can also be used to manage repositories. Zypper works and behaves as a regular command-line tool. It features subcommands, arguments, and options that can be used to perform specific tasks. Zypper offers several benefits compared to graphical package managers. Being a command-line tool, Zypper is faster in use and light on resources. Zypper actions can be scripted. Zypper can be used on systems that do not have graphical desktop environments. This makes it suitable for use with servers and remote machines. The simplest way to execute Zypper is to type its name, followed by a command. Additionally, you can choose from one or more global options by typing them immediately before the command. Some commands require one or more arguments. Executing subcommands in the Zypper shell, and using global Zypper options are not supported.

A decentralized cross-platform software installation system. Works on Linux, Windows and macOS. Fully open-source. Run apps with a single click. Run applications without having to install them first. Control everything from a command line or graphical interface. You control your own computer. You don't have to guess what happens during installation. Mix and match stable and experimental apps on a single system. Anyone can distribute software. Create one package that works on multiple platforms. Publish on any static web host; no central point of control. With dependency handling and automatic updates. Security is central. Installing an app doesn't grant it administrator access. Digital signatures are always checked before new software is run. Apps can share libraries without having to trust each other. Adds automatic self-updating, staged rollouts and various improvements to desktop integration.

This is the code repository for snapd, the background service that manages and maintains installed snaps. Snaps are app packages for desktop, cloud, and IoT that update automatically. Easy to install, secure, cross-platform, and dependency-free. They're being used on millions of Linux systems every day. Alongside its various service and management functions, snapd provides the snap command that's used to install and remove snaps and interact with the wider snap ecosystem, implements the confinement policies that isolate snaps from the base system and from each other, governs the interfaces that allow snaps to access specific system resources outside of their confinement. If you're looking for something to install, such as Spotify or Visual Studio Code, take a look at the Snap Store. And if you want to build your own snaps, start with our creating a snap documentation.

The Secure Universal Package Manager. Continuously govern and audit all packages in your DevOps lifecycle. Thousands of teams worldwide trust MyGet with their package management and governance. Accelerate your software team with cloud package management, robust security controls and easy continuous integration build services. MyGet is a Universal Package Manager that integrates with your existing source code ecosystem and enables end-to-end package management. Centralized package management delivers consistency and governance to your DevOps workflow. MyGet real-time software license detection tracks your teams’ package usage and detects dependencies across all of your packages. Customized usage policies ensure your teams are only using approved packages while reporting vulnerabilities and outdated packages early in your software build and release cycles.

DPKG is a tool to install, build, remove and manage Debian packages. The primary and more user-friendly front-end for DPKG is aptitude. DPKG itself is controlled entirely via command line parameters, which consist of exactly one action and zero or more options. The action parameter tells DPKG what to do and options control the behavior of the action in some way. DPKG can also be used as a front-end to DPKG-deb(1) and DPKG-query. The list of supported actions can be found later on in the actions section. If any such action is encountered DPKG just runs DPKG-deb or DPKG-query with the parameters given to it, but no specific options are currently passed to them, to use any such option the back-ends need to be called directly. DPKG maintains some usable information about available packages. The information is divided into three classes, states, selection states, and flags. These values are intended to be changed mainly with dselect.

Helm helps you manage Kubernetes applications, Helm charts help you define, install, and upgrade even the most complex Kubernetes application. Charts are easy to create, version, share, and publish, so start using Helm and stop the copy-and-paste. Charts describe even the most complex apps, provide repeatable application installation, and serve as a single point of authority. Take the pain out of updates with in-place upgrades and custom hooks. Charts are easy to version, share, and host on public or private servers. Use helm rollback to roll back to an older version of a release with ease. Helm uses a packaging format called charts. A chart is a collection of files that describe a related set of Kubernetes resources. A single chart might be used to deploy something simple, like a memcached pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.

Create native MSIX packages, build clean installs, and build installations in the cloud with InstallShield from Revenera. Consistent and reliable installs. Every time. With InstallShield, you’ll adapt to industry changes quickly, get to market faster and deliver an engaging customer experience. Revenera InstallShield (formerly Flexera InstallShield) is the fastest easiest way to build Windows installers and MSIX packages and create installations directly within Microsoft Visual Studio. Configure install conditions to specifically target Windows 11 and Windows Server 2022. Install files to native ARM locations on Windows 10 running on ARM machines. Easily move your build infrastructure to the cloud by connecting to Revenera’s Cloud License Server. Build one-click installers that are more modern than ever and refreshingly simple. Configure pre-requisites to install third-party packages from Microsoft’s Windows Package Manager.

You can manage your Windows PCs (Windows 7 and later) in a live web interface with Ninite Pro. Install the lightweight Ninite Agent on your machines and they instantly appear on the web for simple point-and-click management. It's an easy way to get a real-time interactive view of all your machines. The new Ninite Pro lets you manage your software in a live web interface. Each machine is a row and each app is a column. You can select an individual cell to update, install, or uninstall an app on a machine. Or select many cells (or whole rows or columns or everything) to perform bulk actions. You can even watch the agents work in real-time. The agent receives commands and sends back updates over a secure connection to Ninite's servers. This means that a roaming laptop looks and works just like any other machine in the web interface. It also makes it possible to issue install/update/uninstall commands for offline machines and have them be delivered the next time those machines are online.

The Industry Standard Universal Binary Repository Manager. Supports all major package types (over 27 and growing) such as Maven, npm, Python, NuGet, Gradle, Go, and Helm including Kubernetes and Docker as well as integration with leading CI servers and DevOps tools that you already use. Additional functionalities include: - High Availability that scales to infinity with active/active clustering of your DevOps environment and scales as business grows - On-Prem, Cloud, Hybrid, or Multi-Cloud Solution - De Facto Kubernetes Registry managing application packages, operating system’s component dependencies, open source libraries, Docker containers, and Helm charts with full visibility of all dependencies. Compatible with a growing list of Kubernetes cluster providers.

Scan for vulnerabilities and control who can access different feeds and actions, all within minutes of download and fast install. ProGet is self-managed and is available in a powerful free version that can be upgraded as needed. ProGet helps you package applications and components so you can ensure your software is built only once, and then deployed consistently across environments. This means everyone can be certain that what goes to production is exactly what was built and tested. Third-party packages (such as NuGet, npm, PowerShell, and Chocolatey) and Docker containers are also supported, allowing you to enforce quality standards, monitor for open-source licenses, and scan for vulnerabilities across all packages, much earlier in the development cycle. With high availability, load-balancing, and multi-site replication, ProGet can centralize your organization’s software applications and components to provide uniform access to developers and servers.

Give your teams a single source of truth for every component they use. Optimize build performance and reliability by caching proxies of remote repositories. Deliver universal coverage for all major package types and formats. Install on an unlimited amount of servers for an unlimited amount of users. Store and distribute Maven/Java, npm, NuGet, Helm, Docker, P2, OBR, APT, GO, R, Conan components and more. Manage components from dev through delivery, binaries, containers, assemblies, and finished goods. Awesome support for the Java Virtual Machine (JVM) ecosystem, including Gradle, Ant, Maven, and Ivy. Streamline productivity by sharing components internally. Gain insight into component security, license, and quality issues. Build off-line with remote package availability. Integrate with industry-leading build tools. Nexus Repository Pro capabilities for your binaries and build artifacts across the entire software supply chain.

Codeberg is a collaboration platform and git hosting for free and open source software, content and projects. Independent and powered by your donations and contributions - consider joining the non-profit association Codeberg e. V. to further support our mission and receive your vote! All services run on servers under our control, no dependencies on external services and no third party cookies, no tracking. While all successful software tools that enabled this development were contributed by the Free and Open Source Software community, commercial for-profit platforms dominate the hosting of the results of our collaborative work. This has led to the paradox that literally millions of volunteers create, collect, and maintain invaluable knowledge, documentation, and software, to feed closed platforms driven by commercial interests, whose program is neither visible nor controllable from outside.

Perforce version control — Helix Core — tracks and manages changes to your source code, digital assets, and large binary files. But it does so much more than that. Helix Core helps development teams move faster, even as they develop more complex products. And it provides a single source of truth across development. Contributors can sync their work into Helix Core from the tools they’re already using. Plus, Helix Core can handle everything. 10s of thousands of users. 10s of millions of daily transactions, 100s of terabytes of data. And 10,000+ concurrent commits. It can even deliver files quickly to remote users without the WAN wait. And it can be used on-premises or in the cloud. Spend less time dealing with tools and processes — and more time delivering value. Helix Core ensures that everyone is efficient. You'll get fast feedback, flexibility, and automation for faster builds. Stop wasting your developers’ time with manual workflows — and let them get back to coding.

fpm is a tool that lets you easily create packages for Debian, Ubuntu, Fedora, CentOS, RHEL, Arch Linux, FreeBSD, macOS, and more! fpm isn’t a new packaging system, it’s a tool to help you make packages for existing systems with less effort. It does this by offering a command-line interface to allow you to create packages easily. FPM is written in ruby and can be installed using gem. For some package formats (like rpm and snap), you will need certain packages installed to build them. Some package formats require other tools to be installed on your machine to be built; especially if you are building a package for another operating system/distribution. FPM takes your program and builds packages that can be installed easily on various operating systems. It can take any nodejs package, ruby gem, or even a python package and turn it into a deb, rpm, pacman, etc. package.

Synaptic is a graphical package management program for apt. It provides the same features as the apt-get command-line utility with a GUI front-end based on Gtk+. Install, remove, upgrade and downgrade single and multiple packages. Upgrade your whole system. Manage package repositories (sources.list). Find packages by name, description, and several other attributes. Select packages by status, section, name, or a custom filter. Sort packages by name, status, size, or version. Browse all available online documentation related to a package. Download the latest changelog of a package. Lock packages to the current version. Force the installation of a specific package version. Undo/Redo selections. Built-in terminal emulator for the package manager. Debian/Ubuntu only, configure packages through the debconf system. Debian/Ubuntu only, Xapain-based fast search (thanks to Enrico Zini).

A blazingly fast and futuristic package manager for windows. Unlike any other package manager, Novus uses multithreaded downloads making the download speeds 8 times faster. Apart from being extremely fast, Novus also installs and uninstalls packages concurrently, making it as efficient as possible. Not only are all of Novus’s packages are monitored regularly, but all of them are always up to date and trusted by the community. Apart from being extremely fast, Novus also installs and uninstalls packages concurrently, making it as efficient as possible. Not only are all of Novus’s packages are monitored regularly, but all of them are always up to date and trusted by the community.

pkgsrc is a framework for managing third-party software on UNIX-like systems, currently containing over 17,900 packages. It is the default package manager of NetBSD and SmartOS and can be used to enable freely available software to be built easily on a large number of other UNIX-like platforms. The binary packages that are produced by pkgsrc can be used without having to compile anything from the source. It can be easily used to complement the software on an existing system. pkgsrc is very versatile and configurable, supporting building packages for an arbitrary installation prefix, allowing multiple branches to coexist on one machine, a build options framework, and a compiler transformation framework, among other advanced features. Unprivileged use and installation are also supported. NetBSD already contains the necessary tools for using pkgsrc; on other platforms, you need to bootstrap pkgsrc to get the package management tools installed.

eoPKG is the package manager for the Solus operating system. It is used to manage installed software packages, search for available software, and to apply updates to the system. Change the system root for eoPKG commands. Set username used when connecting to Basic-Auth repositories. Set password used when connecting to Basic-Auth repositories. Enable full debug information and backtraces. Keep bandwidth usage under the specified (numeric) KBs. Disable the use of ANSI escape sequences for colorization by eoPKG. On success, 0 is returned. A non-zero return code signals a failure.

Scoop installs programs you know and love, from the command line with a minimal amount of friction. For terminal applications, Scoop creates shims, a kind of command-line shortcuts, inside the ~\scoop\shims folder, which is accessible in the PATH. For graphical applications, Scoop creates program shortcuts in a dedicated Start menu folder, called 'Scoop Apps'. This way, packages are always cleanly uninstalled and you can be sure what tools are currently in your PATH and in your Start menu.