Package Manager Status

Package Manager Status

Last updated: 2026-06-20

This page tracks the current state of Cmder packages in Windows package managers. The canonical GitHub issue for coordinating official ownership, blockers, and release workflow work is:

• cmderdev/cmder#3094

The official Cmder install path is still the latest GitHub release. Package-manager entries listed below may be community-maintained unless noted otherwise.

Current State

Package manager	Commands	Current status	Ownership status
WinGet	Not available yet. winget search --query cmder --source winget currently returns no Cmder package.	Needs a manifest PR to microsoft/winget-pkgs. WinGet now supports ZIP archive packages with portable nested installers, so Cmder no longer needs a separate installer before an initial WinGet package can be attempted.	No current package. Cmder core team approval is needed before presenting any package as official.
Chocolatey	choco install cmder or choco install cmdermini	Packages exist at 1.3.25: Cmder and cmdermini.	Community-maintained, not currently owned by cmderdev. Current package source links point to @AdmiringWorm's automatic/cmder and automatic/cmdermini. The nuspec owners list AdmiringWorm, dtgm.
Scoop	scoop install cmder or scoop install cmder-full	Manifests exist at 1.3.25 in ScoopInstaller/Main: cmder.json and cmder-full.json.	Community-maintained in Scoop's main bucket, but already uses official Cmder release assets and hashes.

Plan

The goal is to make package-manager installation predictable for users while preserving Cmder's portable model.

1. Keep #3094 open as the master package-manager tracking issue.
2. Keep existing open package-manager issues open and link them back to the master issue and this wiki page.
3. Add package-manager release assets/templates to the Cmder repository so a release can generate the same metadata every time.
4. For WinGet, submit initial manifests for both full and mini packages after the core team approves the package identity.
5. For Chocolatey, contact the current package maintainers and ask them to add Cmder maintainers or coordinate a transfer. Chocolatey's vendor guidance asks software authors/vendors to contact current maintainers first; if there is no response after 7 days, contact Chocolatey site admins with the contact history.
6. For Scoop, continue using ScoopInstaller/Main unless the core team decides to create an official bucket. The Main manifests are already discoverable and already point to Cmder release assets.

Proposed Package IDs

These are proposed, not final:

• WinGet full: Cmder.Cmder
• WinGet mini: Cmder.CmderMini
• Chocolatey full: keep Cmder
• Chocolatey mini: keep cmdermini
• Scoop mini: keep cmder
• Scoop full: keep cmder-full

For WinGet, the full package should use the cmder.zip release asset and target x64, because the full Cmder archive vendors 64-bit Git for Windows. The mini package should use cmder_mini.zip and can likely target neutral.

Relevant Issues

• #3094 - master package-manager tracking issue.
• #2552 - active WinGet feature request.
• #2355 - older WinGet pipeline request, closed as duplicate of #2552.
• #959 - older Chocolatey ownership/update discussion.
• #762 - older Chocolatey package support request.
• #42 - early Scoop/package-manager discussion.
• #1818 - installer/updater proposal.
• #2729 - installer/MSI request.

External References

• WinGet manifest creation
• WinGet manifest submission
• WinGet archive installer schema
• Chocolatey vendor/author package guidance
• Chocolatey package triage process
• Chocolatey maintainer handover guidance