Automic VaultAutomic Vault

brew

emqx mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install emqx

local Homebrew formula metadata

Überblick

Paketzusammenfassung

MQTT broker for IoT

Befehle und Aliase

  • emqx
  • emqx-5.8.8
  • emqx_cluster_rescue
  • emqx_ctl
  • emqx_ctl-5.8.8
  • emqx_fw
  • install_upgrade.escript
  • install_upgrade.escript-5.8.8
  • no_dot_erlang.boot
  • node_dump
  • nodetool-5.8.8

Verlauf

Projektgeschichte und Nutzung

EMQX is an Erlang-based MQTT broker and IoT messaging platform for high-scale device connectivity, MQTT protocol support, clustering, rules, data integrations, and operational management.

Projektgeschichte

EMQ's tenth-anniversary post says EMQX was released as an open-source project on GitHub on December 17, 2012. The same source frames its origin around Erlang, MQTT, and open source, and says development continued through the 2010s as MQTT became a default protocol for IoT messaging.

The official history highlights several product milestones: early MQTT 3.1 and 3.1.1 compatibility, EMQX 3.0 in 2018 with full MQTT 5.0 server support, EMQX 4.0 in 2020 with a built-in SQL-based rule engine, and EMQX 5.0 with larger-scale clustering, MQTT over QUIC, and 100M+ connection testing.

The README describes EMQX as a platform rather than only a broker, with support for MQTT 5.0, 3.1.1, and 3.1, plus MQTT-SN, CoAP, LwM2M, and MQTT over QUIC. It also documents the 5.9.0 licensing/product change that unified features from the previous open-source and enterprise editions under BSL 1.1.

Adoptionsgeschichte

The anniversary post gives the clearest official adoption snapshot: more than 10K GitHub stars, more than 20M downloads, more than 20,000 enterprise users, and more than 30,000 active cluster deployments per month at the time of that post.

EMQX's commercial adoption story is also official: EMQ says the company opened in 2017 in response to enterprise users deploying EMQX at scale, and the anniversary post cites over 400 customers and over 70 Fortune 500 companies using EMQX in IoT, IIoT, connected-vehicle, and other mission-critical applications.

Wie es verwendet wird

Package users run EMQX as a broker service, commonly exposing MQTT ports, the Dashboard, and HTTP APIs. The official README shows Docker startup, Kubernetes operator documentation, downloads for self-managed installs, and build-from-source instructions.

Configuration became more HOCON-oriented in EMQX 5. The official configuration docs describe `etc` as the static configuration directory, `data/configs` as the dynamic runtime configuration directory, `base.hocon` for configuration-as-code, `cluster.hocon` for changes persisted through Dashboard/API/CLI, and `emqx.conf` for backward-compatible immutable settings.

In deployed systems, EMQX is commonly used as the MQTT ingress and routing layer for IoT data, with rules and bridges sending messages to Kafka, RabbitMQ, PostgreSQL, MySQL, MongoDB, Redis, ClickHouse, cloud messaging services, webhooks, and observability systems.

Warum Paket-Nerds sich dafür interessieren

EMQX is a heavier package-manager entry than most CLIs in this batch: it ships a broker, management commands, Erlang runtime expectations, configuration layers, a dashboard, and service-style deployment behavior. For package maintainers, it sits closer to Redis, RabbitMQ, or Mosquitto than to a single-purpose command.

It matters to package nerds because it exposes the messy but useful intersection of package managers and distributed systems: local development installs, service supervision, data directories, versioned config migration, and network ports all have to line up before the binary is useful.

Zeitleiste

  • 2012: EMQX released as an open-source project on GitHub on December 17.
  • 2017: EMQ opened as a company after enterprise deployment demand grew.
  • 2018: EMQX 3.0 released with complete MQTT 5.0 server support.
  • 2020: EMQX 4.0 introduced a built-in SQL-based rule engine.
  • 2022: EMQX 5.0 arrived with 100M+ connection testing and MQTT over QUIC highlighted by EMQ.
  • v5.9.0: EMQX unified prior open-source and enterprise features under BSL 1.1.

Related projects

  • Related EMQ projects and surfaces include EMQX Cloud, the EMQX Kubernetes Operator, MQTTX, the EMQX rule engine and data integrations, and the broader MQTT broker ecosystem that includes Mosquitto, VerneMQ, HiveMQ, and RabbitMQ MQTT plugins.

Sicherheitslage

Risikostufe: orange

formula declares a Homebrew service. infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • formula declares a Homebrew service
  • infrastructure mutation or orchestration signal

Signale

  • metadata:service
  • text:cluster

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Formelmetadaten deklarieren einen Service- oder Daemon-Block.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 7 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
etc/emqx.confetc/base.hoconetc/cluster.hocon

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
emqxcliglobales Executable
emqx-5.8.8cliglobales Executable
emqx_cluster_rescuecliglobales Executable
emqx_ctlcliglobales Executable
emqx_ctl-5.8.8cliglobales Executable
emqx_fwcliglobales Executable
install_upgrade.escriptcliglobales Executable
install_upgrade.escript-5.8.8cliglobales Executable
no_dot_erlang.bootcliglobales Executable
node_dumpcliglobales Executable
nodetool-5.8.8cliglobales 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-Version5.8.8
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv5.8.8

https://github.com/emqx/emqx

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:emqx
Version5.8.8
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/emqx
Homepagehttps://www.emqx.io/
Repositoryhttps://github.com/emqx/emqx
Upstream-Dokumentationhttps://docs.emqx.com/en/emqx/latest
LizenzApache-2.0
Quellarchivhttps://github.com/emqx/emqx/archive/refs/tags/v5.8.8.tar.gz
Abhängigkeitenopenssl@3
Build-Abhängigkeitenautoconf, automake, cmake, coreutils, erlang@26, freetds, libtool
Von macOS bereitgestellte Bibliothekencyrus-sasl, krb5, ncurses
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstdeclared

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameemqx
Version Scheme0
Revision0
Conflicts With
  • cassandra
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • stable

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
  • package relationship graph
  • package version freshness
  • package-page enrichment