Automic VaultAutomic Vault

brew

brpc mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install brpc

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Better RPC framework

Befehle und Aliase

  • parallel_http
  • rpc_press
  • rpc_replay
  • rpc_view
  • trackme_server

Verlauf

Projektgeschichte und Nutzung

Apache bRPC is an industrial-grade C++ RPC framework for reliable, high-performance services. It is rooted in Baidu production infrastructure and later became an Apache Top-Level Project, with built-in support for multiple protocols, observability endpoints, benchmarking and replay tools, and distributed-systems components.

Projektgeschichte

The Apache bRPC website describes the project as an industrial-grade C++ RPC framework often used in high-performance systems such as search, storage, machine learning, advertising, and recommendation. The README explains the name as better RPC and highlights one-port multi-protocol servers, HTTP/HTTPS, h2/gRPC, Redis, memcached, Thrift, Baidu internal protocols, and braft-based Raft services.

bRPC entered the Apache Incubator on 2018-11-13. The incubator status page records Apache bRPC incubating releases 0.9.6 in 2019, 0.9.7 in 2020, 1.0.0 in 2021, and 1.1.0 through 1.3.0 in 2022 before graduation on 2022-12-22. The first listed post-graduation Apache bRPC release is 1.4.0 on 2023-02-07.

Adoptionsgeschichte

bRPC's adoption history starts inside Baidu: the official docs include use-case pages for Baidu Maps API gateway, Union DSP, ELF learning framework, and cloud-platform proxy services. After incubation, adoption broadened through Apache governance, public documentation, mailing lists, GitHub issues, and Homebrew packaging.

Unlike many RPC libraries packaged primarily as language modules, bRPC ships developer-facing tools such as `rpc_press`, `rpc_replay`, `rpc_view`, `parallel_http`, and `trackme_server`, which explains why it appears as a Homebrew formula rather than only as a C++ source dependency.

Wie es verwendet wird

Engineers use bRPC to build C++ clients and servers that need high-throughput RPC, mixed protocol support, HTTP-accessible debugging, profiling, load balancing, naming-service integration, and production observability. It is especially relevant to large internal-service deployments where one framework must bridge custom protocols and common open protocols.

Warum Paket-Nerds sich dafür interessieren

For package nerds, bRPC is a useful contrast to small CLI tools: it is a heavy C++ distributed-systems framework whose package-manager artifact exposes both libraries and operational tools. Its history also shows how company-born infrastructure becomes a community-governed Apache project without losing the fingerprints of its original production environment.

Zeitleiste

  • Pre-2018: bRPC develops as Baidu production RPC infrastructure.
  • 2018-11-13: bRPC enters the Apache Incubator.
  • 2019-07-14: Apache bRPC incubating 0.9.6 release.
  • 2021-10-31: Apache bRPC incubating 1.0.0 release.
  • 2022-12-22: bRPC graduates from the Apache Incubator.
  • 2023-02-07: Apache bRPC 1.4.0 release after graduation.

Related projects

  • Related projects include gRPC, Apache Thrift, protobuf, braft, Redis and memcached clients, HTTP/2 service frameworks, and other large-scale C++ RPC stacks used inside infrastructure companies.

Sicherheitslage

Risikostufe: yellow

broad file, network, media, or database tool signal. generalized runtime or code generation signal.

Risikoklassifikator

yellow Risiko · mittel Konfidenz · runtime

Warum

  • broad file, network, media, or database tool signal
  • generalized runtime or code generation signal

Signale

  • text:http,server
  • text:repl

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 5 Laufzeitabhängigkeiten.
  • 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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
parallel_httpcliglobales Executable
rpc_presscliglobales Executable
rpc_replaycliglobales Executable
rpc_viewcliglobales Executable
trackme_servercliglobales 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-10
Manager-Version1.17.0
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://brpc.apache.org/

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:brpc
Version1.17.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/brpc
Homepagehttps://brpc.apache.org/
Repositoryhttps://github.com/apache/brpc
Upstream-Dokumentationhttps://brpc.apache.org/docs
LizenzApache-2.0
Quellarchivhttps://www.apache.org/dyn/closer.lua?path=brpc/1.17.0/apache-brpc-1.17.0-src.tar.gz
Zuletzt aktualisiert2026-06-22T14:02:55-07:00
Pulseupdated
Abhängigkeitenabseil, gflags, leveldb, openssl@3, protobuf@33
Build-Abhängigkeitencmake
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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