Automic VaultAutomic Vault

brew

kubecm mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install kubecm

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#kubecm

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

Überblick

Paketzusammenfassung

KubeConfig Manager

Verlauf

Projektgeschichte und Nutzung

KubeCM is a kubeconfig manager for Kubernetes users who work with multiple clusters, namespaces, and context files. It wraps common kubeconfig chores such as listing, switching, merging, deleting, and distributing configurations behind an interactive CLI.

Projektgeschichte

The sunny0826/kubecm repository was created on 2019-07-23, and the first GitHub release, v0.0.1, was published on 2019-07-25. The README describes the project plainly as a way to manage kubeconfig more easily.

As the project evolved, its README highlighted context management, kubeconfig merging, interactive selection, a Git-backed registry for team distribution, multi-platform support, and shell completion.

Adoptionsgeschichte

KubeCM sits in the same everyday-operator niche as kubectx and kubens: tools that reduce friction around switching clusters and namespaces. Its documented install paths include Homebrew, GitHub release binaries, and Krew as the kc plugin, which covers both standalone CLI users and kubectl-plugin users.

Wie es verwendet wird

The tool is centered on ~/.kube/config and related kubeconfig files. Users employ it to switch contexts, merge files, clean up entries, and share cluster access definitions through the registry feature.

Because kubeconfig files may contain sensitive access material, KubeCM is operationally adjacent to credentials even though it does not define a separate credentials store of its own.

Warum Paket-Nerds sich dafür interessieren

KubeCM is package-nerd-significant as a quality-of-life CLI rather than as infrastructure plumbing. It packages a pile of tiny kubeconfig edits into one cross-platform binary that can be installed with Homebrew or Krew and carried across developer machines.

Its popularity reflects a Kubernetes reality: once users touch many clusters, the kubeconfig file becomes a database they need tools to query, merge, and prune.

Zeitleiste

  • 2019-07-23: GitHub repository created.
  • 2019-07-25: GitHub release v0.0.1 published.
  • 2019-07-26: GitHub release v0.0.2 published.
  • 2026-03-09: GitHub release v0.35.1 published.

Related projects

  • kubectl is the command-line client whose kubeconfig state KubeCM helps manage.
  • Krew distributes KubeCM as the kc kubectl plugin.
  • kubectx and kubens are adjacent context and namespace switching tools in the same operator-workflow space.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • 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
~/.kube/config

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
kubecmcliglobales 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-07-25
Manager-Version0.35.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.35.1

https://github.com/sunny0826/kubecm

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:kubecm
Version0.35.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/kubecm
Homepagehttps://kubecm.cloud
Repositoryhttps://github.com/sunny0826/kubecm
Upstream-Dokumentationhttps://github.com/sunny0826/kubecm#readme
LizenzApache-2.0
Quellarchivhttps://github.com/sunny0826/kubecm/archive/refs/tags/v0.35.1.tar.gz
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 Namekubecm
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%

kubecm

nix profile install nixpkgs#kubecm
  • normalized package name match
  • Abgeglichen nach: Kubecm
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ku/kubecm/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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
  • Nucleus package database
  • av.db category and tag curation
  • 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