Automic VaultAutomic Vault

brew

Installer emqx avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de emqx pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install emqx

local Homebrew formula metadata

aperçu

Résumé du paquet

MQTT broker for IoT

Commandes et alias

  • 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

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : orange

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

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

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

Signaux

  • metadata:service
  • text:cluster

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de formule déclarent un service ou daemon.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • S’installe avec 1 dépendances d’exécution.
  • Les métadonnées de compilation listent 7 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

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

exécutables

Exécutables installés

CommandeTypeExpositionNote
emqxcliexécutable global
emqx-5.8.8cliexécutable global
emqx_cluster_rescuecliexécutable global
emqx_ctlcliexécutable global
emqx_ctl-5.8.8cliexécutable global
emqx_fwcliexécutable global
install_upgrade.escriptcliexécutable global
install_upgrade.escript-5.8.8cliexécutable global
no_dot_erlang.bootcliexécutable global
node_dumpcliexécutable global
nodetool-5.8.8cliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire5.8.8
gestionnaire mis à jour
données localesOK
amontà jour
dernière version détectéev5.8.8

https://github.com/emqx/emqx

  • infoNo package-manager update timestamp was available.confiance faible

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:emqx
Version5.8.8
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/emqx
Page d'accueilhttps://www.emqx.io/
Dépôthttps://github.com/emqx/emqx
Docs amonthttps://docs.emqx.com/en/emqx/latest
LicenceApache-2.0
Archive sourcehttps://github.com/emqx/emqx/archive/refs/tags/v5.8.8.tar.gz
Dépendancesopenssl@3
Dépendances de compilationautoconf, automake, cmake, coreutils, erlang@26, freetds, libtool
Bibliothèques fournies par macOScyrus-sasl, krb5, ncurses
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Servicedeclared

faits du registre

Détails de la base source

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

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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