pkg.soopen package index

brew / Rang 4974

helmsman mit Homebrew, Nix, zypper installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für helmsman in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install helmsman

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#helmsman

nixpkgs package indexes · pkgs/by-name/he/helmsman/package.nix · Quelle: api.github.com

openSUSE zypperverifiziert · 92%
sudo zypper install helmsman

openSUSE Tumbleweed package metadata · helmsman · Quelle: download.opensuse.org

Überblick

Paketzusammenfassung

Helm Charts as Code tool

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.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für helmsman wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 2 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

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.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
./*.toml./*.yaml./*.yml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
helmsmancliglobales Executable

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-09-19
Manager-Version4.0.5
Manager aktualisiert2026-09-12
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv4.0.5

https://github.com/mkubaczyk/helmsman

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:helmsman
Version4.0.5
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/helmsman
Homepagehttps://github.com/mkubaczyk/helmsman
Repositoryhttps://github.com/mkubaczyk/helmsman
LizenzMIT
Quellarchivhttps://github.com/mkubaczyk/helmsman/archive/refs/tags/v4.0.5.tar.gz
Zuletzt aktualisiert2026-09-12T01:14:19Z
Pulseupdated
Abhängigkeitenhelm, kubernetes-cli
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namehelmsman
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

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
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/he/helmsman/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
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
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: helmsman from https://download.opensuse.org/tumbleweed/repo/oss/repodata/d310d5a96106e1e8872a385adf98aaa23be9db5d80937a6717314e7e7f37715065c6c748ab7ccee6475d620b46979c0fe64235fc0c46988e17edf659578fcf31-primary.xml.zst

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.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation