Automic VaultAutomic Vault

brew

Install havener with Homebrew, MacPorts

Swiss army knife for Kubernetes tasks. Version 2.2.7 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install havener

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install havener

MacPorts ports tree · sysutils/havener/Portfile · source: api.github.com

overview

Package summary

Swiss army knife for Kubernetes tasks

Commands and aliases

  • havener

history

Project history and usage

Havener is a Go command-line convenience wrapper around kubectl for Kubernetes tasks. Its own README describes it as a tool created to shorten long kubectl workflows and provide a Swiss-army-knife style set of cluster operations.

Project history

The project is maintained under the Homeport GitHub organization and documents commands for events, logs, node-exec, pod-exec, top, and watch. The README says it was created because Kubernetes users often end up with long kubectl commands for recurring tasks such as executing commands across pods or retrieving usage details.

Its release list shows a 1.x and 2.x version history, with v2.2.x releases distributed through GitHub. The repository badges and Go module references show the normal Go CLI maintenance pattern: tests, Go Report Card, Go Reference, tagged releases, and source builds with go install.

Adoption history

Havener appears to be a niche Kubernetes operator tool rather than a broad platform. Package metadata shows distribution through Homebrew and MacPorts, and the README documents a Homebrew tap, download script, and go install path.

Adoption is likely concentrated among users who already operate Kubernetes clusters with kubectl and want compact commands for cross-pod execution, log retrieval, event viewing, pod watching, and resource overview tasks.

How it is used

Havener relies on the same Kubernetes configuration model as kubectl: KUBECONFIG can point at a YAML config file, and the --kubeconfig flag can supply a path such as $HOME/.kube/config.

Common commands include havener events, havener logs, havener node-exec, havener pod-exec, havener top, and havener watch. This makes it a companion CLI rather than an independent Kubernetes API surface.

Why package nerds care

For package nerds, Havener is a small example of an opinionated kubectl adjunct being packaged as a standalone Go binary. It depends on the user's existing Kubernetes credentials and cluster access rather than owning credentials or config.

Its significance is modest but practical: Homebrew distribution turns a project-specific operations helper into a repeatable install for macOS and other brew users.

Timeline

  • 1.x: Havener established the Kubernetes helper CLI and tagged early stable releases.
  • 2.x: The project continued with tagged GitHub releases and command documentation.
  • 2024: GitHub release listings show v2.2.x releases through late 2024.
  • 2026: Homebrew metadata and the repository show ongoing package availability.

Related projects

  • kubectl is the primary Kubernetes CLI that Havener wraps for convenience.
  • Kubernetes configuration through KUBECONFIG and kubeconfig files is the authentication and cluster-selection layer Havener relies on.
  • Homeport's other Go CLIs, such as dyff, sit in the same small-operations-tool ecosystem.

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • infrastructure mutation or orchestration signal

Signals

  • text:kubernetes

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
havenercliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version2.2.7
manager updated
local dataok
upstreamcurrent
latest detectedv2.2.7

https://github.com/homeport/havener

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:havener
Version2.2.7
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/havener
Homepagehttps://github.com/homeport/havener
Repositoryhttps://github.com/homeport/havener
Upstream docshttps://github.com/homeport/havener#readme
LicenseMIT
Source archivehttps://github.com/homeport/havener/archive/refs/tags/v2.2.7.tar.gz
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

MacPorts95%

havener

sudo port install havener
  • normalized package name match
  • Matched by: Havener
MacPorts ports tree · api.github.com · MacPorts ports tree: sysutils/havener/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment