A top-tier open source project. Docs, tests, and CI are all in excellent shape.
Protocol Buffers - Google's data interchange format
Documentation
90
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
83
CI is configured (.github/workflows/test_bazel.yml).
Test files detected (bazel/tests).
Lockfile present (examples/go/go.sum). Installs are reproducible.
Linter or formatter configured (csharp/.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (csharp/compatibility_tests/v3.0.0/src/Google.Protobuf.Test/Google.Protobuf.Test.csproj).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository files69 root entries
- .bazelci
- .bcr
- .githubGood: CI is configured (.github/workflows/test_bazel.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- bazelGood: Test files detected (bazel/tests).
- benchmarks
- build_defs
- ci
- cmake
- compatibility
- conformance
- csharpGood: Linter or formatter configured (csharp/.editorconfig).Good: Dependency manifest found (csharp/compatibility_tests/v3.0.0/src/Google.Protobuf.Test/Google.Protobuf.Test.csproj).
- docs
- editions
- editors
- examplesGood: Lockfile present (examples/go/go.sum). Installs are reproducible.
- go
- google3
- hpb
- hpb_generator
- java
- lua
- objectivec
- patches
- php
- pkg
- pythonGood: Environment pinned via python/docs/environment.yml.
- ruby
- rust
- src
- third_party
- toolchain
- upb
- upb_generator
- .bazelignore
- .bazeliskrc
- .bazelrc
- .clang-format
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .readthedocs.yml
- appveyor.bat
- appveyor.yml
- BUILD.bazel
- CMakeLists.txt
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- CONTRIBUTORS.txt
- Disable_bundle_install.patch
- fix_permissions.sh
- generate_descriptor_proto.sh
- global.json
- google3_export_generated_files.sh
- LICENSEGood: Licensed under Other.
- maven_dev_install.json
- maven_install.json
- MODULE.bazel
- PrivacyInfo.xcprivacy
- protobuf_deps.bzl
- protobuf_release.bzl
- protobuf_version.bzl
- protobuf.bzl
- Protobuf.podspec
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- regenerate_stale_files.sh
- SECURITY.mdGood: Security policy present.
- version.json
- WORKSPACE
- WORKSPACE.bzlmod