Website: https://mikeholp87.github.io/update-forge/
A free, open-source (MIT) software updater for Windows 11 (and compatible Windows 10) and Linux. It inventories what is installed, shows which applications have a newer version available, and installs updates through trusted package managers, on demand or on a schedule. No telemetry, no accounts, no ads.
Status: 0.3.4. See Known limitations and docs/ENGINEERING-REPORT.md for exactly what has and has not been tested.
- Discovery: WinGet (installed packages, available versions, pins), Windows uninstall registry (read-only), Microsoft Store/MSIX packages, Scoop, Chocolatey and npm (global packages) when installed.
- Discover packages: search enabled managers and their configured catalogs in parallel, with results appearing as each manager finishes. Recent searches are reused for up to two minutes; Refresh fetches fresh results. Cancellation keeps packages already found. Every result has an Install button for WinGet, Scoop, Chocolatey and npm: it asks for confirmation first, skips packages that are already installed, takes the same lock as update runs so the two never overlap, and records the attempt in History.
- npm: global packages are inventoried, checked against the registry, and updated by installing the exact version that was checked. npm is run as
node.exe npm-cli.jsdirectly (nevernpm.cmdor a shell), package names and versions are validated, and packages installed withnpm linkare treated as held. Permission errors are reported as needing administrator rights. - Honest status: every application is Update ready, Approval required, Manual update, No update method or Unknown. UpdateForge never reports an unknown version as "newer" and never invents installers or switches.
- Update engine: sequential queue, per-item state machine, post-install verification, restart detection, crash recovery (an interrupted install is never reported as success).
- Fluent WPF UI: dashboard, installed applications, queue, history, settings; light/dark; tray icon.
- Package managers: a dedicated page for provider health, installed CLI versions and paths, enabled providers, configured sources, and WinGet/Scoop source refresh. Setup links open each manager's official instructions. Source additions/removals remain CLI operations.
- Scheduling: a per-user Windows Task Scheduler task runs scans (and, if enabled, safe updates) even when the window is closed.
- Export and bundles: export the installed list (or just the updates) to CSV or JSON, from the app or with
updateforge-cli export.updateforge-cli bundle export <file>saves your WinGet packages to a bundle;bundle import <file>shows what is missing and--installinstalls it. Bundles are untrusted input: ids, sources and versions are validated and nothing outside WinGet/msstore is ever run. - CLI:
updateforge-cli scan | list | outdated | update --all | update --id <id> | export | bundle export|import | history | providers | doctor | schedule | diagnostics export(--jsonsupported). - Diagnostics: redacted ZIP for bug reports.
Linux: x64 or arm64 with a desktop session (X11 or Wayland) for the GUI; the CLI runs anywhere. Providers: apt, Flatpak, Snap, npm, pnpm, Bun, Yarn Classic, Cargo, pipx and Homebrew, each used when installed. See Linux.
Windows: Windows 11 x64 (Windows 10 2004+ expected to work, untested). WinGet (App Installer) is needed for update installation.
The Linux build shares the engine, database, CLI and policy with the Windows build. What differs:
- Providers:
apt(packages you installed yourself plus anything upgradable),flatpak(apps, per user and system installation),snap,npm, and the per-user toolspnpm,bun,yarn(Classic 1.x only),cargo(crates fromcargo install),pipxandbrew(Homebrew formulae and casks). The per-user tools are looked up on PATH and in their usual install folders, never run as root, and validate every package name before it reaches a command line. Cargo, Bun, Yarn and pipx have no bulk outdated command, so each package is looked up individually. Cargo updates recompile the crate; pipx and Homebrew always move to the newest release (they cannot pin a version). Debian version ordering (epochs,~) is implemented, so1:2.0correctly beats1.9. - Privileges: apt upgrades need root, so UpdateForge runs
apt-getthroughpkexec(polkit shows the password prompt) and never stores or asks for your password itself. The .deb installs a small helper (/usr/libexec/updateforge/updateforge-apt-helper) with its own polkit action,io.github.mikeholp87.updateforge.apt: the prompt names UpdateForge, asks every time, and covers only "refresh sources" or "install/upgrade one package"; admins can write polkit rules for that action alone. The portable tarball has no helper and uses plainpkexec apt-get. Flatpak and Snap authorize through their own polkit prompts. Scheduled runs never prompt: updates needing authorization stay pending and you are notified. - Scheduling: a systemd user timer (
~/.config/systemd/user/updateforge.timer), no root. It fires while you are logged in;loginctl enable-linger $USERkeeps it running after logout. Battery use maps toConditionACPower, metered connections are read from NetworkManager (nmcli). - Recommendations: a Recommended page (and
updateforge-cli recommend) suggests packages that fit what you already have, with the reason and a usage tip: Proton tooling if you have Steam,needrestartandfwupdif you use apt,git-deltaif you use git. It also points out programs installed through two managers, held-back packages and managers that are switched off. The catalog is reviewed and local: nothing is fetched, ranked by popularity or sent anywhere, every suggestion installs through the same confirmed path as Discover, and you can dismiss any of them for good. It also learns what you are into: programs are sorted into interest areas (gaming, development, video and audio, backups, ...), new installs and the suggestions you accept or turn down adjust a local profile that fades over a few months, and a clear interest brings more suggestions in that area, with the reason. The page shows exactly what it has learned, and you can switch learning off or erase it. - GUI: Avalonia (
updateforge), with a tray icon (GNOME needs the AppIndicator extension) and notifications throughnotify-send. - CLI:
updateforge-cliwith the same commands (scan,outdated,update --all,schedule apply, ...).bundleis WinGet-only and not available. - Data lives in
~/.local/share/UpdateForge(database, logs).
Build and package (needs the .NET 10 SDK):
dotnet build UpdateForge.CI.slnf -c Release
dotnet test --project tests/UpdateForge.Core.Tests
./scripts/publish-linux.sh 0.3.4 # artifacts/*.deb and a portable .tar.gz
sudo apt install ./artifacts/updateforge_0.3.4_amd64.debDebian / Ubuntu (apt): signed repository, updates arrive through apt upgrade.
sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://mikeholp87.github.io/apt/apt.asc | sudo tee /etc/apt/keyrings/mikeholp87-apt.asc >/dev/null
echo "deb [signed-by=/etc/apt/keyrings/mikeholp87-apt.asc] https://mikeholp87.github.io/apt/ ./" | sudo tee /etc/apt/sources.list.d/mikeholp87-apt.list
sudo apt update && sudo apt install updateforgeWindows: release artifacts: per-user MSI (no admin needed) and a portable ZIP, each with SHA-256 sums. Unsigned builds may show a SmartScreen warning; UpdateForge does not suppress it.
Modes: Manual (default, check only) and Automatic Safe (scheduled runs install only supported, non-interactive, non-elevated updates; anything else stays pending and you are notified). Managed Automatic is intentionally disabled until an elevated execution mechanism has been independently tested. The scheduled task never runs as SYSTEM and never elevates.
See SECURITY.md. In short: official package-manager CLIs at fixed paths, strictly validated typed arguments (no shell strings), no --force/hash-bypass flags, pins and holds honored, no automatic restarts.
- Windows cannot update arbitrary third-party software; registry-only apps are inventory-only.
- Store apps: no supported API exists to check or trigger updates for other apps; UpdateForge offers an Open Microsoft Store handoff.
- Packages needing administrator rights are never installed unattended; Chocolatey installs and upgrades require running UpdateForge elevated. Installing from Discover always asks first, and npm packages can run their own install scripts, so check what you install.
- WinGet integration uses the CLI (anchored on locale-independent
winget export), not yet the COM API. - The pnpm, Bun, Yarn Classic, Cargo, pipx and Homebrew providers are on by default on Linux and each is skipped when its tool is not installed (turn them off under Package Managers). They are fixture-tested; Cargo, Bun, Yarn and Homebrew were also run read-only against the real tools, while pnpm and pipx were not (no working install available), so their JSON parsing follows the documented output only. No real update or install was run for any of them.
- Scoop/Chocolatey providers are fixture-tested only, and the npm provider is fixture-tested plus checked read-only against a real npm (listing, search, registry, version check; no real update or install was run). npm must be installed with the standard Node.js layout (nvm and Volta layouts are not supported yet), and Scoop cannot install a specific version; Portable-app provider, self-update, localization, ARM64 and UI automation tests are not implemented yet.
dotnet build UpdateForge.CI.slnf -c Release # everything except the MSI installer, which needs the publish step below
dotnet test --project tests/UpdateForge.Core.Tests
./scripts/publish.ps1 -Version 0.1.0 # portable ZIP
dotnet build src/UpdateForge.Installer/UpdateForge.Installer.wixproj -c Release -p:Version=0.1.0Requires the .NET 10 SDK. See docs/DEVELOPMENT.md and CONTRIBUTING.md.
MIT, see LICENSE.
WPF UI (MIT), TaskScheduler (MIT), Serilog (Apache-2.0), Microsoft.Data.Sqlite (MIT), CommunityToolkit.Mvvm (MIT), WiX Toolset (MS-RL, build-time only). Design informed by public documentation of WinGet, Scoop, Chocolatey, UniGetUI and Patch My PC; no code was copied from them.