Automic VaultAutomic Vault

brew

Installer zyre avec Homebrew

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

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install zyre

local Homebrew formula metadata

aperçu

Résumé du paquet

Local Area Clustering for Peer-to-Peer Applications

Commandes et alias

  • zpinger

historique

Historique du projet et usages

Zyre is a ZeroMQ-family C framework for local-area peer discovery, presence, and reliable group messaging. It lets nearby processes find each other over a LAN, join groups, and exchange messages without a central broker.

Historique du projet

The public zeromq/zyre repository was created on 2012-10-17 inside the broader ZeroMQ ecosystem. Its README presents Zyre as local-area clustering for peer-to-peer applications, built around UDP beacons for discovery and ZeroMQ Dealer-Router messaging for reliable peer interconnection.

Zyre is closely tied to ZeroMQ's RFC process. The README points to RFC 36, the ZeroMQ Realtime Exchange protocol, for discovery and heartbeating; that stable RFC defines how peers discover each other, organize into groups, and send events over ZMTP.

The project inherited common ZeroMQ community practices: MPL 2.0 source, C4-style contribution process, CLASS C style guidance, generated API documentation, self-tests, and example tools such as zpinger for seeing peers on a local network.

Historique d'adoption

Zyre adoption sits in the ZeroMQ niche rather than in general application networking. The README lists use cases such as local service discovery, clustering services on the same Ethernet network, smart-device control, and multi-user mobile applications, which are exactly the places where brokerless local discovery is useful.

The ZeroMQ Guide's distributed-computing chapter frames discovery, presence, and connectivity as recurring problems for room-scale, WiFi, and proximity networks. Zyre packages one opinionated answer to that problem for C and ZeroMQ users, so its significance is strongest for developers already comfortable with ZeroMQ patterns.

Modes d'utilisation

A Zyre application creates a node, starts it, receives event messages, joins or leaves named groups, whispers to individual peers, and shouts to groups. The README describes incoming events as zmsg_t messages delivered by zyre_recv, with the first frame identifying event type.

The bundled zpinger utility is the package's practical command-line face: running it on two or more machines is the README's smoke test for local discovery. Library users build the same primitives into local clusters, device-control networks, and peer-aware services.

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

Zyre is package-nerd significant because it is a small leaf in a layered messaging stack: libsodium, libzmq, czmq, then Zyre. Packaging it preserves a higher-level ZeroMQ pattern that would otherwise be reimplemented badly in each local-discovery application.

It is also a good example of protocol-backed packaging. The library is not just helper code; it is an implementation of a published ZeroMQ RFC, which gives downstreams a stable conceptual contract even if their only visible executable is zpinger.

Chronologie

  • 2012-10-17: Public zeromq/zyre GitHub repository is created.
  • 2010s: Zyre grows as the ZeroMQ local-area discovery and clustering layer, with tagged public releases and generated README/API documentation.
  • 2014: RFC 36/ZRE carries 2009-2014 iMatix copyright text and is published as the stable ZeroMQ Realtime Exchange protocol used by Zyre.
  • 2020s: The repository remains active and the README continues to document Linux, macOS, and Windows builds plus zpinger-based local-network testing.

Related projects

  • Related projects and protocols include ZeroMQ/libzmq, CZMQ, libsodium, ZMTP, RFC 36/ZRE, RFC 22/C4, RFC 21/CLASS, zmsg, zactor, zyre_event, zpinger, and other brokerless service-discovery systems such as ZeroConf-style local discovery.

posture de sécurité

Niveau de risque : orange

infrastructure mutation or orchestration signal.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • infrastructure mutation or orchestration signal

Signaux

  • 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 bottle Homebrew sont disponibles pour 13 plateformes.
  • S’installe avec 2 dépendances d’exécution.
  • Les métadonnées de compilation listent 1 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.

exécutables

Exécutables installés

CommandeTypeExpositionNote
zpingercliexé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-10
version du gestionnaire2.0.1
gestionnaire mis à jour2026-06-19
données localesOK
amontnot checked
dernière version détectéenon détecté

https://github.com/zeromq/zyre

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:zyre
Version2.0.1
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/zyre
Page d'accueilhttps://github.com/zeromq/zyre
Dépôthttps://github.com/zeromq/zyre
Docs amonthttps://github.com/zeromq/zyre#readme
LicenceMPL-2.0
Archive sourcehttps://github.com/zeromq/zyre/releases/download/v2.0.1/zyre-2.0.1.tar.gz
Dernière mise à jour2026-06-19T12:33:05-07:00
Pulseupdated
Dépendancesczmq, zeromq
Dépendances de compilationpkgconf
Bouteilledisponible (sur arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namezyre
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • 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 package history
  • package relationship graph
  • package version freshness
  • package-page enrichment