Ross ROSS = Recommend OSS · open-source software intelligence for agents

google/flatbuffers

FlatBuffers: Memory Efficient Serialization Library observed · 2026-08-28

github.com/google/flatbuffers · homepage · C++ · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

84/100

  • Activity 97
  • Release rhythm 57
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 38.5
  • age_days: 4489
  • days_rel: 208
  • days_push: 22
  • n_releases_24m: 7

Full methodology

Adoption not part of the score

26411 stars · 3633 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

FlatBuffers is Google's cross-platform, memory-efficient serialization library that stores data in a binary format you can read directly without a parsing or unpacking step. It ships a schema compiler (flatc) that generates accessors and builders for many languages, including C++, Java, C#, Go, Python, Rust, and JavaScript, with forwards/backwards schema compatibility.

Use cases

  • serialize data efficiently across multiple programming languages
  • read serialized data with zero-copy, no parsing or unpacking
  • fast binary serialization for games and performance-critical apps
  • evolve a data schema while keeping backwards and forwards compatibility
  • replace protocol buffers or JSON with a faster binary format
  • convert JSON into a compact binary representation
  • access large serialized files via memory-mapped buffers on mobile or embedded devices

When to choose

  • you need maximum memory efficiency and speed in serialization hot paths
  • you must exchange structured data between different languages or schema versions
  • you target game development, Android, or embedded systems where footprint and allocation matter
  • you want to read buffers directly without per-object heap allocations

When to avoid

  • you need human-readable output or easy ad-hoc introspection, where JSON is a better fit
  • your data is fully dynamic with no schema known ahead of time
  • you rely on the broad RPC and tooling ecosystem of protocol buffers
  • you want a trivial setup for small configs where JSON or YAML suffices

Facets

library · maturity stable

serialization compiler parser developer-tools mobile-development embedded-systems performance cross-platform cpp c rust go python jvm dotnet embedded zero-copy schema-compiler flatc code-generation binary-format schema-evolution grpc protobuf-alternative mmap memory-efficiency json-conversion game-development android ios

2 sources

Member repositories

RepositoryRoleHealth v2
google/flatbuffersmain84

For agents

markdown · JSON · MCP: product_card(name="google/flatbuffers")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem