macOS
Homebrewverifiziert · 100%
brew install helmsmanlocal Homebrew formula metadata
brew / Rang 4940
helmsman mit Homebrew, Nix, zypper installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für helmsman in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Linux
Nixverifiziert · 92%
nix profile install nixpkgs#helmsmannixpkgs package indexes · pkgs/by-name/he/helmsman/package.nix · Quelle: api.github.com
openSUSE zypperverifiziert · 92%
sudo zypper install helmsmanopenSUSE Tumbleweed package metadata · helmsman · Quelle: download.opensuse.org
Überblick
Paketzusammenfassung
Helm Charts as Code tool
Projektlinks
Befehle und Aliase
- helmsman
Verlauf
Projektgeschichte und Nutzung
Helmsman is a 'Helm Charts as Code' CLI for managing Helm releases from a declarative desired state file. It plans, validates, and applies a set of chart releases, using Helm and Kubernetes tooling underneath.
Projektgeschichte
The `mkubaczyk/helmsman` repository was created in 2017 and early releases followed quickly, with a 0.1.0 release in November 2017 and a 1.0.0 release in March 2018. The README describes the tool as a way to automate deployment and management of Helm charts from version-controlled code.
Helmsman uses a desired state file, originally centered on TOML and also accepting YAML, to define repositories, namespaces, releases, protection settings, and execution order. Its README emphasizes plan/view/apply behavior, idempotency, namespace and release protection, priority ordering, and parallel execution.
The README records a stewardship change from Praqma, later Eficode, to the maintainers of the `mkubaczyk/helmsman` repository. Later documentation distinguishes Helmsman major lines by Helm compatibility, with v1.x for Helm 2 and v4.x for Helm 3 and Helm 4.
Adoptionsgeschichte
Helmsman gained attention in the same era as Helmfile: Kubernetes users had many Helm charts to deploy, but wanted a declarative file and a plan step instead of shell scripts full of `helm install` commands. Its packaging through Homebrew and other distributions reflects use as a local or CI command-line deployment tool.
Wie es verwendet wird
Users run `helmsman -f example.toml` to plan, `helmsman --apply -f example.toml` to execute, and flags such as `--dry-run`, `--debug`, and `--target` to inspect or limit changes. A binary install expects `kubectl`, `helm`, and for many versions the `helm-diff` plugin.
The tool can run as a binary, as a container in CI, or as a container inside a Kubernetes cluster. Its value is strongest where release ordering, namespace protection, and repeated idempotent application matter.
Warum Paket-Nerds sich dafür interessieren
Helmsman is part of the Helm wrapper generation that treated Kubernetes releases as package sets. For package-minded operators, its desired-state file is the manifest of packages, while Helm remains the lower-level package manager.
The explicit major-line mapping to Helm 2, Helm 3, and Helm 4 makes it a good example of a wrapper whose own packaging has to track another package manager's compatibility surface.
Zeitleiste
- 2017: The `mkubaczyk/helmsman` repository was created and 0.1.0 was released.
- 2018: Helmsman v1.0.0 was published.
- 2025: Helmsman v4.0.0 was published with documentation for Helm 3 and Helm 4 support.
Related projects
- Helm is the chart manager Helmsman orchestrates.
- kubectl is a runtime prerequisite for binary use.
- helm-diff is listed by the README as a required plugin for Helmsman versions from 1.6.0 onward.
Quellen
Sicherheitslage
Noch keine Protected-Tool-Abdeckung gefunden
Für helmsman wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Installationsverhalten
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
helmsman | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-08-03
Manager-Version4.0.5
Manager aktualisiert2026-07-27
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:helmsman |
|---|---|
| Version | 4.0.5 |
| Paketmanager | Homebrew |
| Homepage | https://github.com/mkubaczyk/helmsman |
| Repository | https://github.com/mkubaczyk/helmsman |
| Zuletzt aktualisiert | 2026-07-27T14:32:24+02:00 |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Andere Paketmanager-Einträge
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
Nix95%
helmsman
nix profile install nixpkgs#helmsman- normalized package name match
- Abgeglichen nach: Helmsman
zypper95%
helmsman 3.17.1-1.8
Helm Charts as Code
https://github.com/Praqma/helmsman
sudo zypper install helmsman- License: MIT
- Category: Unspecified
- Architecture: x86_64
- Source Package: helmsman
- 2 Abhängigkeiten
- 1 stellt bereit
- normalized package name match
- Abgeglichen nach: Helmsman
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation