Automic VaultAutomic Vault

brew

Install avro-cpp with Homebrew, Nix

Data serialization system. Version 1.12.1 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install avro-cpp

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#avro-cpp

nixpkgs package indexes · pkgs/by-name/av/avro-cpp/package.nix · source: api.github.com

overview

Package summary

Data serialization system

Commands and aliases

  • avrogencpp

history

Project history and usage

Avro C++ is Apache Avro's C++ binding and code-generation package. In Homebrew it is the small native companion to the broader Avro project, centered on the avrogencpp executable and C++ API documentation.

Project history

Apache Avro reached its first official release as Avro 1.0.0 in July 2010. Its design centered on a shared schema specification, binary encoding, object container files, and language bindings so data could move between systems without each implementation inventing its own wire format.

The C++ binding follows that multi-language model inside the main Apache Avro repository. It lets C++ programs use Avro records and schemas directly, while avrogencpp gives statically typed C++ projects generated code from Avro schemas.

Adoption history

Avro adoption grew around data pipelines that need compact records and schema evolution. Apache's own site now positions Avro as a leading record serialization format and emphasizes streaming data pipelines, which explains why package managers keep separate language/runtime formulas.

The C++ package is most relevant where native services want Avro compatibility without a JVM runtime. It is less famous than avro-tools, but it matters in packaging because generated headers, libraries, and ABI concerns are different from shipping a Java jar.

How it is used

Typical usage is schema-first: write or receive an Avro schema, generate C++ types with avrogencpp when useful, then serialize or deserialize records through the C++ library. For dynamic or inspection workflows, users often pair it with the separate Java or C command-line tools.

Avro C++ does not have a documented global config file or credential file. Schemas, generated code, and application-level settings are the practical configuration surface.

Why package nerds care

avro-cpp is a good example of why one upstream project can produce several formulas. The source tree and release cadence are shared with Apache Avro, but the build products are native C++ libraries and a generator binary, so downstream packagers treat it differently from avro-c and avro-tools.

It is also a useful litmus test for multi-language serialization projects: if the C++ binding builds cleanly and tracks the shared specification, the format is more credible outside JVM-centered data stacks.

Timeline

  • 2010: Apache Avro 1.0.0 announced as the first Avro release.
  • 2021: Avro 1.11.0 released with a large set of project fixes and features.
  • 2024: Avro 1.12.0 released by the Apache Avro community.
  • 2025: Avro 1.12.1 listed as the latest Apache Avro release.

Related projects

  • avro-c provides the neighboring native C implementation and file utilities.
  • avro-tools provides Java command-line utilities for schema and data-file work.
  • Other Apache Avro bindings include JVM languages, Python, C#, PHP, Ruby, Rust, JavaScript, and Perl.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 2 runtime dependencies.
  • Build metadata lists 3 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
avrogencppcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version1.12.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://avro.apache.org/

  • infoNo package-manager update timestamp was available.low confidence
  • infoRelease/tag comparison is only available for GitHub repositories.https://avro.apache.org/none confidence

install metadata

Package metadata

Package keybrew:avro-cpp
Version1.12.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/avro-cpp
Homepagehttps://avro.apache.org/
Repositoryhttps://github.com/apache/avro
Upstream docshttps://avro.apache.org/docs
LicenseApache-2.0
Source archivehttps://www.apache.org/dyn/closer.lua?path=avro/avro-1.12.1/cpp/avro-cpp-1.12.1.tar.gz
Dependenciesboost, zstd
Build dependenciescmake, fmt, pkgconf
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameavro-cpp
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

avro-cpp

nix profile install nixpkgs#avro-cpp
  • normalized package name match
  • Matched by: Avro Cpp
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/av/avro-cpp/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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