Automic VaultAutomic Vault

brew

hivemind mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install hivemind

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#hivemind

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

Überblick

Paketzusammenfassung

Process manager for Procfile-based applications

Befehle und Aliase

  • hivemind

Verlauf

Projektgeschichte und Nutzung

Hivemind is a Go process manager for Procfile-based development applications. It reads a Procfile, starts multiple named processes, and uses pseudo-terminals so logs behave like terminal output rather than buffered file output.

In package-manager culture it is a small, sharp alternative to heavier Procfile managers: install the binary, run it in a project directory, and get color-preserving, low-lag process output for local development stacks.

Projektgeschichte

The Hivemind repository begins on 2015-04-08 with an initial commit. Early commits added process supervision, command-line arguments, working-directory support, improved errors, and README material. The v1.0 tag appeared on 2016-06-03, followed by maintenance releases through v1.1.0 in 2021.

The README explains the motivation in relation to Procfile tools such as David Dollar's Foreman. Procfile-based tools simplify multi-process application development, but many process managers make child processes think they are writing to a file, which can cause lag, lost or broken colored output, and extra log decoration. Hivemind was created to fix those problems by using ptys to capture output.

Hivemind later became the smaller sibling in a pair with Overmind. The Hivemind README points users who need tmux integration, individual process restarts, process killing, and advanced configuration to Overmind, while keeping Hivemind focused on the simpler Procfile runner use case.

Adoptionsgeschichte

Hivemind's adoption is strongest among web application developers who use Procfile conventions for local stacks: a web server, worker, frontend builder, queue processor, or other long-running process groups. The README names Heroku and Deis as popular platforms that helped establish the Procfile format.

Homebrew and Nix packaging made Hivemind easy to install in developer environments, especially on macOS. Its official README also documents pre-built release binaries and source installation with Go.

The Evil Martians article linked from the README positioned Hivemind and Overmind as tools the team used over Foreman-style managers for Procfile-based development, giving the project an authoritative adoption story in Rails and full-stack development circles.

Wie es verwendet wird

A Hivemind user creates a Procfile with lines such as `web: bin/rails server`, `worker: bundle exec sidekiq`, and `assets: gulp watch`, then runs `hivemind` in the same directory. A custom file such as `Procfile.dev` can be passed as an argument.

The README documents `.env` support for variable assignments and states that every Hivemind option can be set through a corresponding environment variable. It supports Linux, FreeBSD, and macOS.

Warum Paket-Nerds sich dafür interessieren

Hivemind is package-nerd-significant because it is a minimal process manager with one job: run Procfile processes correctly in a terminal. It deliberately avoids Overmind's tmux-centered feature set, which makes it attractive when a package user wants Foreman-like behavior without a Ruby dependency or tmux session.

It also shows how small developer tools often enter package managers: the problem is not algorithmic novelty but operational fit. Hivemind preserves colored output, avoids log clipping and delays, reads familiar Procfiles and `.env` files, and ships as a simple Go-built binary.

Zeitleiste

  • 2015-04-08: Repository history begins with the initial commit.
  • 2015-04: Early commits add process management, CLI flags, working-directory support, and README material.
  • 2016-06-03: v1.0 is tagged.
  • 2017-08-07: Evil Martians publishes an article introducing Overmind and Hivemind.
  • 2017-2021: Maintenance releases continue through v1.1.0.

Related projects

  • Foreman is the Procfile manager named by the Hivemind README as the tool that started the pattern.
  • Overmind is Hivemind's larger sibling, adding tmux support and more advanced process control.
  • Heroku and Deis are named by the README as platforms that popularized Procfile conventions.

Quellen

  • Evil Martians article linked by the README for author/team context and Hivemind/Overmind introduction.
  • Official Git repository tags and commits for timeline dates.
  • Official Hivemind README for motivation, supported platforms, install, Procfile usage, `.env`, and relation to Foreman and Overmind.
  • Official Overmind README for the sibling-project relationship and overlapping Procfile context.

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 13 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
ProcfileProcfile.dev.env

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
hivemindcliglobales 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-08
Manager-Version1.1.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.1.0

https://github.com/DarthSim/hivemind

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:hivemind
Version1.1.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/hivemind
Homepagehttps://github.com/DarthSim/hivemind
Repositoryhttps://github.com/DarthSim/hivemind
Upstream-Dokumentationhttps://github.com/DarthSim/hivemind#readme
LizenzMIT
Quellarchivhttps://github.com/DarthSim/hivemind/archive/refs/tags/v1.1.0.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namehivemind
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%

hivemind

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