Search Results for "packages"

...This way, packages are always cleanly uninstalled and you can be sure what tools are currently in your PATH and in your Start menu.

Commando VM (by Mandiant) is a Windows-based offensive security / red-team distribution built to turn a fresh Windows installation into a fully featured penetration testing environment. It provides an automated installer (PowerShell script) that uses Chocolatey, Boxstarter, and MyGet package feeds to download, install, and configure dozens (100+ / 170+ depending on version) of offensive, fuzzing, enumeration, and exploitation tools. The idea is to spare testers the repetitive work of...

...Some commands require extra dependencies which are unavailable in some platforms. You may need to install them manually. Note that only the Homebrew package is maintained by the git-extras developers directly. Other packages are maintained by the distribution's packagers or third-party volunteers. Installing from Homebrew will not give you the option omit certain git-extras if they conflict with existing git aliases. To have this option, build from source.

Scoop «Extras» is the community-maintained bucket of additional manifests for Scoop, the popular Windows command-line installer; it contains packages and app manifests that don’t fit the stricter criteria of the main Scoop bucket. The repository is organized as a large collection of individual manifest files, helper scripts, and tooling to validate and publish new manifests, and it’s intended so users can extend Scoop with many community-contributed applications. Installation is straightforward for Scoop users: add the bucket with scoop bucket add extras and then install any manifest with scoop install <manifest>, making it quick to access a wide range of Windows command-line and GUI tools. ...

...It contains tens of thousands of manifest files (organized under a manifests/ folder) plus schema, validation, CI pipelines, and tooling to build, test, and publish packages so users can install software with a single command. The repo enforces contribution processes (including a Contributor License Agreement flow for many contributors), automated validation checks, and publishing pipelines so manifests meet format, checksum, and licensing expectations before becoming available to users. Maintainers document manifest authoring, testing, and request workflows, and the repository requires installers to be packaged as supported installer formats (MSIX, MSI, APPX, or executable installers), with script-based installers and fonts noted as unsupported.

PowerHub is a PowerShell-based automation framework designed to centralize and orchestrate common administrative tasks across Windows environments. It exposes a modular command set for inventorying systems, managing services, deploying packages, and executing remote commands with consistent logging and error handling. The project places emphasis on discoverability and reuse: scripts are organized into reusable modules and functions with clear parameter contracts so teams can compose higher-level workflows without duplicating glue code. Authentication and remoting are handled idiomatically via PowerShell remoting or credential stores, enabling both interactive and scheduled runs. ...

...The downloads are kept in a cache folder to be used for reinstalls. The downloads are also available for limited use using n which and n run and n exec. The global npm packages are not changed by the install, with the exception of npm itself which is part of the Node.js install.