Repository navigation
CmdWarden 0.12.0
Make AI coding agents ask before they use your CLI secrets on Windows.
Install
| Way | Command or file |
|---|---|
| winget | winget install BasantPandey.CmdWarden (when the winget catalog has this version) |
| Setup zip | Download CmdWarden.0.12.0-setup.zip, extract it, double-click install.cmd |
| Portable zip | Extract CmdWarden.0.12.0-win-x64.zip and run cw.exe |
| dotnet tool | Download CmdWarden.0.12.0.nupkg to a folder, then dotnet tool install -g CmdWarden --add-source <folder> (needs the .NET 10 SDK) |
The winget package, the setup zip, and the portable zip carry their own .NET runtime. No .NET install and no admin prompt.
Then run cw setup. It sets up everything and shows a real Approval Gate card.
Signature
This release is not signed yet: Windows SmartScreen may warn. Compare the sha256 of the zip with this page. A signed release shows Valid here:
Get-ChildItem "$env:LOCALAPPDATA\CmdWarden\app" -Recurse -Include cw.exe, CmdWarden.*.exe |
Get-AuthenticodeSignature | Format-Table Status, PathWhere it came from
GitHub signs a build provenance record for each file of this release. Check that a file came from this repo and its release workflow:
gh attestation verify CmdWarden.0.12.0-setup.zip --repo BasantPandey/CmdWardenCmdWarden.0.12.0.intoto.jsonl holds the same records, for a check with no network: add --bundle CmdWarden.0.12.0.intoto.jsonl.
CmdWarden.0.12.0.cdx.json is the SBOM in CycloneDX format. It lists each package in the portable zip.
Update and remove
cw update installs the newest release after a sha256 check. A winget install updates with winget upgrade BasantPandey.CmdWarden.
cw uninstall removes CmdWarden and every change it made.
Code signing policy
Read the Code signing policy: who signs CmdWarden, and how.