Automic VaultAutomic Vault

brew

blueutil mit Homebrew, MacPorts, Nix installieren

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

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install blueutil

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install blueutil

MacPorts ports tree · sysutils/blueutil/Portfile · Quelle: api.github.com

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#blueutil

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

Überblick

Paketzusammenfassung

Get/set bluetooth power and discoverable state

Befehle und Aliase

  • blueutil

Verlauf

Projektgeschichte und Nutzung

blueutil is a long-running macOS command-line utility for reading and changing Bluetooth state: power, discoverability, paired and connected devices, device info, pairing, connection, and output formats for scripts.

Projektgeschichte

blueutil was originally written by Frederik Seiffert and later maintained by Ivan Kuchin, as recorded in the README copyright section. The GitHub repository dates back to 2011, with v1.0.0 tagged in 2012 and a continuing v2.x release line.

The tool grew from simple power and discoverability controls into a broader Bluetooth scripting interface. The README documents private IOBluetooth framework use, root-user safeguards, JSON output formats, device connection operations, wait commands, and an experimental system_profiler fallback for some paired-device queries.

Adoptionsgeschichte

blueutil became the standard package-manager answer for 'control Bluetooth from a shell on macOS.' Its README documents Homebrew and MacPorts installs, and the input metadata also records a Nix package, reflecting adoption by both casual Mac users and reproducible-environment users.

Its role persisted because macOS does not expose all of these Bluetooth controls through a stable, script-friendly built-in CLI, so package managers filled the gap with a small native utility.

Wie es verwendet wird

Users run blueutil with flags such as --power, --discoverable, --paired, --connected, --info, --connect, --disconnect, --pair, and --unpair. Output can be human-readable or JSON, making it useful in shell scripts, status bars, automation tools, and troubleshooting flows.

The README warns that it uses private IOBluetooth preference APIs and documents macOS-version quirks such as favorite/recent-device behavior starting with macOS 12 Monterey.

Warum Paket-Nerds sich dafür interessieren

blueutil is the classic tiny Mac systems package: one binary that unlocks automation around a GUI-controlled OS feature. Package nerds care because it has survived macOS Bluetooth API changes, packaging across Homebrew/MacPorts/Nix, architecture transitions, and years of shell-script dependence.

It also illustrates the maintenance burden of packaging native Mac utilities: private frameworks, root behavior, TCC/API access failures, output formats for scripts, and compatibility notes all live in a very small command-line surface.

Zeitleiste

  • 2011: GitHub repository created for blueutil.
  • 2012: v1.0.0 tag published.
  • 2018: v2.0.0 tag published.
  • 2021: README documents macOS 12 Monterey behavior changes for favorite and recent devices.
  • 2025: v2.13.0 tag and README copyright show continued maintenance.

Related projects

  • blueutil-tui is documented by the README as a text user interface built on top of blueutil.
  • Homebrew, MacPorts, and Nix are package-manager channels recorded for installation.
  • macOS IOBluetooth and system_profiler are the platform interfaces used or offered as alternatives.

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.

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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
blueutilcliglobales 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-Version2.13.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.13.0

https://github.com/toy/blueutil

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:blueutil
Version2.13.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/blueutil
Homepagehttps://github.com/toy/blueutil
Repositoryhttps://github.com/toy/blueutil
Upstream-Dokumentationhttps://github.com/toy/blueutil#readme
LizenzMIT
Quellarchivhttps://github.com/toy/blueutil/archive/refs/tags/v2.13.0.tar.gz
Bottleverfügbar (auf arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameblueutil
Version Scheme0
Revision0
Head VersionHEAD
Requirements
  • macos
  • xcode
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%

blueutil

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

blueutil

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

Paketgraph

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

Gleicher Workflow

  • bluetoothconnectorShares av.db curated category or tags: bluetooth, cli, macos, system.
  • asitopShares av.db curated category or tags: cli, macos, system.
  • bluezShares av.db curated category or tags: bluetooth, cli, system.
  • brightnessShares av.db curated category or tags: cli, macos, system.
  • cliclickShares av.db curated category or tags: cli, macos, system.
  • dark-modeShares av.db curated category or tags: cli, macos, system.

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 package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment