protocolbuffers/protobuf
Protocol Buffers - Google's data interchange format
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
5 releases in the last 90 days, the latest 1 day ago, with 367 contributors on GitHub.
Peaked at #72 in the weekly ranking the week of Mar 22, its best in the past year.
Use Cases & Benefits
- Provides a language-neutral, platform-neutral mechanism for serializing structured data using Protocol Buffers.
- Enables efficient, extensible, and compact data interchange across multiple programming languages and platforms.
- Use for defining and serializing structured data in distributed systems requiring cross-language communication.
- Use for building RPC systems that need fast and reliable message serialization and deserialization.
- Use for generating code from .proto files to ensure consistent data formats in multi-language microservices.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Other
GitHub could not identify this license; read the LICENSE file before depending on it.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
- License not identified by GitHub; read the LICENSE file before depending on it.
General guidance from repository metadata, not legal advice. How we score
From the README
Copyright 2023 Google LLC
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can learn more about it in protobuf's documentation.
This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.
Most users will find working from supported releases to be the easiest path.
If you choose to work from the head revision of the main branch your build will occasionally be broken by source-incompatible changes and insufficiently-tested (and therefore broken) behavior.
If you are using C++ or otherwise need to build protobuf from source as a part of your project, you should pin to a release commit on a release branch.
This is because even release branches can experience some instability in between release commits.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
+332 stars over 74 days across 8 snapshot days; best day +59 on Sep 3.
Forks
16.4K+98
Open issues
414+101
Compared with peers in Developer Tools
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| stablyai/orca | 121.4K | +6.7K | 75 | today |
| DietrichGebert/ponytail | 188.4K | +4.4K | 75 | 12 days ago |
| affaan-m/ECC | 300.8K | +4.3K | 75 | 40 days ago |
| herdrdev/herdr | 50.0K | +2.1K | 75 | 27 days ago |
| max-sixty/worktrunk | 12.4K | +1.9K | 75 | 21 days ago |
| protocolbuffers/protobuf | 72.2K | — | 75 | 1 day ago |
| Category median | 121.4K | +4.3K | 75 | — |
Discover Repositories
Search across tracked repositories by name or description