google/flatbuffers
Grade a repo

89

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 14% of 5,156 graded repos

FlatBuffers: Memory Efficient Serialization Library

Documentation79
Engineering94
Health97
C++26,210Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    Install and run instructions9pt

    Add a section showing how to install dependencies.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

79

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt64

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

94

Reproducibility6pt82

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/build.yml).

Tests18pt100

Test files detected (dart/test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt90

Dependency manifest found (Package.swift).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 2 / 10
    Commits (30d / 90d)
  • 3,601
    Forks
  • 45
    Releaseslatest 9y ago

Community

  • 100% - Good
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 26,210
    Watchers

Responsiveness

  • 12h
    Median issue response
  • 1d 3h
    Median PR merge time
  • 244
    Open issues
Repository files63 root entries
  • .bazelci
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • android
  • bazel
  • benchmarks
  • CMake
  • dart
    Good: Test files detected (dart/test).
  • docs
  • examples
  • go
  • goldens
  • grpc
  • include
  • java
  • js
  • kotlin
  • lobster
  • lua
  • mjs
  • net
  • nim
  • php
  • python
  • reflection
  • rust
  • samples
  • scripts
  • snap
  • src
  • swift
  • tests
  • ts
  • .bazelignore
  • .bazelrc
  • .clang-format
  • .clang-tidy
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • build_defs.bzl
  • BUILD.bazel
  • CHANGELOG.md
  • CMakeLists.txt
  • composer.json
  • CONTRIBUTING.md
    Good: 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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • eslint.config.mjs
  • extensions.bzl
  • FlatBuffers.podspec
  • Formatters.md
  • library.json
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MODULE.bazel
  • package.json
  • Package.swift
    Good: Dependency manifest found (Package.swift).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • swift.swiftformat
  • tsconfig.json
  • tsconfig.mjs.json
  • typescript.bzl
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/google/flatbuffers)](https://www.repo-grade.com/report/google/flatbuffers)

More graded C++ repos