pkg.soopen package index

brew / Rang 7041

qbec mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install qbec

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#qbec

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

Überblick

Paketzusammenfassung

Configure Kubernetes objects on multiple clusters using jsonnet

Befehle und Aliase

  • qbec

Verlauf

Projektgeschichte und Nutzung

qbec is a Jsonnet-based command-line tool for generating and applying environment-specific Kubernetes objects across clusters and namespaces.

Projektgeschichte

qbec was developed to generate and manage Kubernetes objects across multiple clusters or namespaces, with configuration specialized for a selected target environment. It uses Jsonnet as its data-templating and composition language.

The project explicitly positions itself near kubecfg and ksonnet while providing an application-oriented workflow for initializing configuration, rendering manifests, comparing them with a cluster, and applying or deleting resources. It is maintained in Splunk's GitHub organization.

Adoptionsgeschichte

qbec is distributed as cross-platform release binaries and through Homebrew and Nix. Its placement in the Splunk GitHub organization and dedicated documentation site provide it with a vendor-maintained home while retaining an Apache-licensed open-source workflow.

Wie es verwendet wird

A project is initialized around `qbec.yaml`, environment definitions, and Jsonnet components and parameters. Operators select an environment, render or validate objects, compare desired state with a cluster, and then apply or delete resources.

qbec is useful when several clusters or namespaces share a common configuration model but need target-specific parameters. Kubernetes access follows the operator's normal cluster context and credentials rather than a qbec-specific credentials file.

Warum Paket-Nerds sich dafür interessieren

qbec represents the Jsonnet branch of Kubernetes configuration tooling: configuration remains programmable and composable while a CLI provides environment selection, diffing, application, and deletion. Package users value it as a focused alternative to template-heavy or abandoned Jsonnet-era tools.

Zeitleiste

  • Origins: qbec was created around Jsonnet-based, multi-environment Kubernetes configuration.
  • Project adoption: The project moved under or is maintained by Splunk and gained a dedicated documentation site.
  • Distribution: Cross-platform release binaries and package-manager installations became available.

Related projects

  • Jsonnet is qbec's configuration language.
  • Kubernetes is the deployment target.
  • kubecfg and ksonnet are related Jsonnet-based Kubernetes configuration tools named by qbec's official repository.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:kubernetes,cluster

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
<application root>/qbec.yaml<application root>/params.libsonnet

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
qbeccliglobales 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-Version0.31.0
Manager aktualisiert2026-09-13
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.31.0

https://github.com/splunk/qbec

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:qbec
Version0.31.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/qbec
Homepagehttps://qbec.io
Repositoryhttps://github.com/splunk/qbec
Upstream-Dokumentationhttps://qbec.io
LizenzApache-2.0
Quellarchivhttps://github.com/splunk/qbec/archive/refs/tags/v0.31.0.tar.gz
Zuletzt aktualisiert2026-09-13T19:57:51Z
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 Nameqbec
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%

qbec

nix profile install nixpkgs#qbec
  • normalized package name match
  • Abgeglichen nach: Qbec
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/qb/qbec/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
  • 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