Winpkg -

New hire gets a laptop, runs winpkg bootstrap https://team/winpkgfile.yaml , and 10 minutes later has Node, Python, Docker, VS Code, and all CLI tools ready. No “works on my machine” excuses.

For decades, the Windows software lifecycle followed a predictable—and painful—pattern: hunt down a .exe or .msi on a website, click through a wizard with six "Next" buttons, reboot, and repeat. While Linux users have been apt-get install -ing for a generation, Windows teams have been drowning in entropy. winpkg

👉 github.com/winpkg/winpkg 👉 Discuss: Join our #winpkg channel on Discord New hire gets a laptop, runs winpkg bootstrap

winpkg audit --report json exports every installed package, version, and installation source. Your security team will finally stop asking for screenshots. Getting Started winpkg is available now via GitHub Releases. Installation is one command: While Linux users have been apt-get install -ing

Stop downloading installers. Start declaring your environment.

# As Administrator Set-ExecutionPolicy Bypass -Scope Process -Force [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072 iex ((New-Object System.Net.WebClient).DownloadString('https://get.winpkg.dev/install.ps1')) Then try:

winpkg search python winpkg install python --version=3.12 winpkg run python -- --version We’re shipping winpkg sync (two‑way state sync between machines) and winpkg bundle (create a self‑contained .exe with all dependencies for offline distribution). The roadmap is public and community‑driven. Final Thought Windows is a fantastic development and enterprise OS. It just needed a package manager that took software supply chains seriously. winpkg closes that gap.