Automic VaultAutomic Vault

brew

litmusctl mit Homebrew, Nix installieren

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

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install litmusctl

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#litmusctl

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

Überblick

Paketzusammenfassung

Command-line interface for interacting with LitmusChaos

Befehle und Aliase

  • litmusctl

Verlauf

Projektgeschichte und Nutzung

litmusctl is the command-line companion to LitmusChaos, a CNCF-hosted cloud-native chaos engineering platform. It matters less as a standalone tool than as the terminal interface for connecting Chaos Delegates, creating projects, scheduling Chaos Scenarios, and managing LitmusChaos accounts.

Projektgeschichte

LitmusChaos began as Kubernetes-oriented chaos engineering tooling before becoming a CNCF project. The separate litmusctl repository was created on February 15, 2021, after Litmus had already entered CNCF Sandbox, giving operators a Go-based CLI for the agent-plane workflows around Litmus ChaosCenter and Kubernetes clusters.

The litmusctl README documents versioned usage guides spanning early v0.2-era compatibility through later v0.12-v0.23 and 1.x releases, which reflects its role as a compatibility-sensitive operations tool tied to LitmusChaos control-plane versions.

Adoptionsgeschichte

Litmus itself was accepted into CNCF on June 25, 2020 and moved to Incubating on January 11, 2022. That CNCF path gave the surrounding tools, including litmusctl, a place in cloud-native SRE workflows rather than only in vendor-specific chaos demos.

The broader Litmus project advertises adopters and end-user case studies, while litmusctl adoption is mostly implicit: users who run LitmusChaos in Kubernetes clusters need a supported CLI path for delegate connection and account operations.

Wie es verwendet wird

litmusctl is used to connect Chaos Delegates, create projects, schedule Chaos Scenarios, disconnect delegates, and manage multiple LitmusChaos accounts. Its documented requirements include a kubeconfig at ~/.kube/config and kubectl underneath for applying manifests.

For package users, the key operational detail is version compatibility: the README maps litmusctl releases such as 1.19.0 through 1.26.0 to supported Chaos Center version ranges.

Warum Paket-Nerds sich dafür interessieren

For Homebrew and Nix users, litmusctl is a small example of a cloud-native project's operational surface being shipped as a standalone CLI, separate from the heavier Kubernetes control plane it manages.

It also shows the package-manager problem of distributing fast-moving Kubernetes ecosystem CLIs whose usefulness depends on a compatibility matrix rather than only on their own version number.

Zeitleiste

  • 2017: LitmusChaos work began as simple Kubernetes chaos jobs, according to CNCF project history.
  • 2020-06-25: Litmus was accepted into CNCF.
  • 2021-02-15: The litmuschaos/litmusctl GitHub repository was created.
  • 2022-01-11: Litmus moved to CNCF Incubating.
  • 2026-05-20: The litmusctl repository listed release 1.26.0.

Related projects

  • LitmusChaos is the parent chaos engineering platform; ChaosHub provides reusable chaos experiments; kubectl and Kubernetes are required context for delegate installation and cluster operations.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für litmusctl wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-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.
  • 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

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.kube/config

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
litmusctlcliglobales 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-Version1.27.0
Manager aktualisiert2026-07-16
lokale DatenOK
Upstreamaktuell
neueste erkannte Version1.27.0

https://github.com/litmuschaos/litmusctl

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:litmusctl
Version1.27.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/litmusctl
Homepagehttps://litmuschaos.io
Repositoryhttps://github.com/litmuschaos/litmusctl
Upstream-Dokumentationhttps://docs.litmuschaos.io/
LizenzApache-2.0
Quellarchivhttps://github.com/litmuschaos/litmusctl/archive/refs/tags/1.27.0.tar.gz
Zuletzt aktualisiert2026-07-16T09:32:18Z
Pulseupdated
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 Namelitmusctl
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%

litmusctl

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

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Verwandte Tools

  • goBuild dependency declared by Homebrew.

Gleicher Workflow

  • chaoskubeShares av.db curated category or tags: chaos-engineering, cli, cloud-infrastructure, kubernetes.
  • openshift-cliShares av.db curated category or tags: cli, cloud-infrastructure, kubernetes.
  • apache-brooklyn-cliShares av.db curated category or tags: cli, cloud-infrastructure.
  • crossplaneShares av.db curated category or tags: cli, cloud-infrastructure, cloud-native, kubernetes.
  • devspaceShares av.db curated category or tags: cli, cloud-infrastructure, cloud-native, kubernetes.
  • egctlShares av.db curated category or tags: cli, cloud-infrastructure, cloud-native, kubernetes.

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