reallyme-buffa-build
This package is part of ReallyMe Buffa, an independent fork of upstream Buffa maintained by ReallyMe Technologies Limited for secret-bearing protobuf messages.
The fork adds opt-in mechanisms for guarded field storage, zeroization, controlled JSON export, and cleanup of sensitive messages and selected well-known types. We publish this fork on crates.io under separate reallyme-* package names so applications can pin and consume these features through Cargo while we maintain the fork and propose the changes upstream.
Secret handling requires explicit configuration and suitable owning types. It is not automatic. Transport buffers, parser scratch, and copies outside those owners remain the application's responsibility.
Compatibility: this is separately versioned from upstream and is not an unchanged repackaging of Buffa 0.9.2. Use the matching ReallyMe runtime and generator, and regenerate protobuf bindings when migrating.
Upstream direction: our preference is to use upstream Buffa. If upstream provides equivalent secret-handling capabilities and guarantees, and our applications can migrate safely, we intend to migrate back upstream and retire active development of this fork. Published ReallyMe versions would remain available for reproducible builds.
This is the 0.1.3 ReallyMe release, distributed under Apache-2.0. Upstream license and attribution notices are retained; upstream endorsement is not implied.
Configuration and limits · Migration and provenance
Package role: Generation from build.rs, including selection of guarded representations and cleanup/export policies.
Build-time integration for compiling Protocol Buffers schemas into buffa Rust
types. It runs from your crate's build.rs; generated messages use the
separate buffa runtime crate.
Protobuf compiler
By default, buffa-build runs protoc. Install it on PATH or set the
PROTOC environment variable. The minimum version is v21.12; schemas that use
editions 2023 need v27.0, and schemas that use editions 2024 need v32.0.
To use buf instead, install it and select it with .use_buf(). That mode
needs a buf.yaml at the crate root, ignores .includes(), and takes
.files() paths relative to the buf module directory. You can also pass a
precompiled descriptor set with .descriptor_set().
See the prerequisites section of the user guide for how to install either compiler.
Quick start
Add the runtime and build dependencies. Add buffa-types too when your
schemas use protobuf well-known types such as Timestamp or Any.
Compile your schemas and generate a module tree:
// build.rs
Include the generated modules in your crate:
// src/lib.rs
include_file creates the nested module tree for the protobuf packages,
including packages that refer to one another.
See the user guide for the full set of code generation options.