Public recordAt Risk
Software health reportschema 0.29.0 · metrics 2.10.0 · 2026-08-02 20:14 UTC
pittengermdp / flatbuffers
FlatBuffers: Memory Efficient Serialization Library
pittengermdp/flatbuffers holds a health index of 27 out of 100, placing it in the At Risk band. It scores highest on Vitality (88/100) and lowest on Community & Adoption (12/100). It was last updated 12 days ago. 5 contributors account for most of its recent work.
27
overall / 100Software health index
Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.
27
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
Score profile
Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.
The weighted overall 53 is calibrated to 54 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.
Ownership
pittengermdpPersonal account
1 follower12 public repossince Mar 2023
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| Go | github.com/google/flatbufferspoints to another repo — not scored | v25.12.19+incompatible | - | 48 | 225 days ago | — |
| npm | flatbufferspoints to another repo — not scored | 25.9.23 | 30,037,754 | 38 | 312 days ago | flatbuffers |
| Packagist | google/flatbufferspoints to another repo — not scored | v25.12.19 | 3,977 | 40 | 225 days ago | serializationgoogleflatbuffers |
| Maven | com.google.flatbuffers:flatbuffers-javapoints to another repo — not scored | 25.2.10 | - | 29 | 537 days ago | — |
| PyPI | flatbufferspoints to another repo — not scored | 25.12.19 | - | 26 | 225 days ago | — |
| crates.io | flatbuffers-reflectionpoints to another repo — not scored | 0.1.0 | 12,141 | 1 | 527 days ago | — |
| crates.io | flatbufferspoints to another repo — not scored | 25.12.19 | 6,078,359 | 33 | 225 days ago | flatbuffersserializationzero-copydata-structuresencodingmemory-management |
| crates.io | flexbufferspoints to another repo — not scored | 25.12.19 | 111,398 | 11 | 225 days ago | flatbuffersflexbuffersserializationzero-copydata-structuresencodingmemory-management |
| Maven | com.google.flatbuffers:flatbuffers-java-grpc | 2.0.3 | - | 9 | 1795 days ago | — |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
88
Development activity
80Excellent
How it's scored
| 28.8/36 | Push recency — last push 12 days ago |
| 22.8/36 | Commit cadence — 33/52 weeks with commits |
| 18/18 | Commit volume — 207 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 207 |
| human_commit_share | 0.95 |
| days_since_last_push | 12 |
| active_weeks_last_year | 33 |
Release discipline
100Exceptional
How it's scored
| 27/27 | Ships releases — 4 releases published |
| 36/36 | Release recency — latest release 12 days ago |
| 27/27 | Release cadence — a release every ~6.3 days |
| 10/10 | OpenSSF Scorecard: Signed-Releases — 4 out of the last 4 releases have a total of 4 signed artifacts. |
Inputs used
| releases_count | 4 |
| latest_release_tag | v0.5.3 |
| releases_from_tags | no |
| days_since_latest_release | 12 |
| mean_days_between_releases | 6.3 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
12
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 0 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 0 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
25At Risk
How it's scored
| 0/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | no |
| has_license | no |
| readme_badges | 4 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | github.com, shields.io |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
49
Maintainer resilience (bus factor)
87Excellent
How it's scored
| 45.9/54 | Bus factor — 5 contributor(s) cover half of all commits |
| 17.6/22.5 | Commit distribution — top contributor authored 22% of commits |
| 13.5/13.5 | Contributor breadth — 99 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 22 contributing companies or organizations |
Inputs used
| bus_factor | 5 |
| contributors_sampled | 99 |
| top_contributor_share | 0.217 |
Issue & PR responsiveness
1Critical
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 0/30 | PR acceptance — no decided pull requests or no data |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 0 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | — |
| closed_unmerged_prs | 0 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
34At Risk
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 2.2/25 | Owner reach — 1 followers of pittengermdp |
| 14.9/25 | Track record — 12 public repos, account ~3 yr old |
Inputs used
| followers | 1 |
| owner_type | User |
| is_verified | — |
| owner_login | pittengermdp |
| public_repos | 12 |
| account_age_days | 1,238 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
69Good
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on maven |
| 4/35 | Publish recency — latest publish 1,795 days ago |
| 20/20 | Version history — 9 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | com.google.flatbuffers:flatbuffers-java-grpc |
| ecosystems | maven |
| any_deprecated | no |
| min_days_since_publish | 1,795 |
Engineering Quality
Are baseline engineering and documentation practices in place?
73
Engineering practices
88Excellent
How it's scored
| 24/24 | CI workflows — 7 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — eslint.config.mjs |
| 0/9.6 | Pre-commit hooks |
| 6.4/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | yes |
| has_linter_config | yes |
| has_precommit_config | no |
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
Documentation
50Moderate
How it's scored
| 0/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://flatbuffers.dev/ |
| 0/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | https://flatbuffers.dev/ |
| docs_site | https://flatbuffers.dev/ |
| has_readme | no |
| has_docs_dir | yes |
| has_description | no |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
28
Security posture
28At Risk
Jurisdiction risk alert
High-risk jurisdiction exposure detected
1 top contributor profilesRussia
Based on self-published public profile locations. This governance signal does not determine nationality, citizenship, intent, sanctions status, or individual trustworthiness.
How jurisdiction exposure is assessedHow it's scored
| 6/7.5 | Binary-Artifacts — binaries present in source code |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 22 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 5/5 | Fuzzing — project is fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — no SAST tool detected |
| 5/5 | Security-Policy — security policy file detected |
| 7.5/7.5 | Signed-Releases — 4 out of the last 4 releases have a total of 4 signed artifacts. |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 0/7.5 | Vulnerabilities — 13 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 5.5 |
| high_risk_jurisdiction_cap | 34 |
| high_risk_jurisdiction_multiplier | 50 |
| security_posture_after_multiplier | 28 |
| security_posture_before_jurisdiction | 55 |
Excluded from scoring (no data or not applicable): CI-Tests, Packaging. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.
AI Readiness
How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.
74
Agent context & guidance
40Weak
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 90 of 95 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.947 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
80Excellent
How it's scored
| 18/18 | One-command bootstrap — grpc/samples/greeter/Makefile |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — eslint.config.mjs |
| 11/11 | Static type checking — grpc/examples/ts/greeter/tsconfig.json, python/py.typed, tests/ts/tsconfig.json, tsconfig.json |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 8/8 | Automated maintenance — 5 of the last 100 commits are automated dependency updates |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | pnpm-lock.yaml |
| has_dockerfile | yes |
| typed_language | yes |
| bootstrap_files | grpc/samples/greeter/Makefile |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | grpc/examples/ts/greeter/tsconfig.json, python/py.typed, tests/ts/tsconfig.json, tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | android/app/build.gradle, android/build.gradle, examples/go-echo/go.mod, go.mod, grpc/examples/go/greeter/client/go.mod, grpc/examples/go/greeter/models/go.mod, grpc/examples/go/greeter/server/go.mod, grpc/flatbuffers-java-grpc/pom.xml, grpc/pom.xml, grpc/tests/pom.xml, java/pom.xml, kotlin/benchmark/build.gradle.kts, kotlin/build.gradle.kts, kotlin/convention-plugins/build.gradle.kts, kotlin/flatbuffers-kotlin/build.gradle.kts, net/FlatBuffers/Google.FlatBuffers.csproj, rust/flatbuffers/Cargo.toml, rust/flexbuffers/Cargo.toml, rust/reflection/Cargo.toml, rust/reflection/fuzz/Cargo.toml, samples/go.mod, tests/FlatBuffers.Benchmarks/FlatBuffers.Benchmarks.csproj, tests/FlatBuffers.Test/FlatBuffers.Test.csproj, tests/rust_no_std_compilation_test/Cargo.toml, tests/rust_reflection_test/Cargo.toml, tests/rust_serialize_test/Cargo.toml, tests/rust_usage_test/Cargo.toml, tests/rust_usage_test/outdir/Cargo.toml, tests/union_of_union_test/go.mod |
| dependency_bot_commit_share | 0.05 |
Code legibility for models
98Exceptional
How it's scored
| 45/45 | Type-checkable code — C++ (statically typed) |
| 53.4/55 | Manageable file sizes — 42/1,461 source files over 60KB |
Inputs used
| primary_language | C++ |
| largest_source_bytes | 184,137 |
| source_files_sampled | 1,461 |
| oversized_source_files | 42 |
Machine-readable interfaces
100Exceptional
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — tests/prototest/imported.proto, tests/prototest/non-positive-id.proto, tests/prototest/test.proto, tests/prototest/twice-id.proto, tests/prototest/use-reserved-id.proto |
| 0/20 | MCP server — not applicable to this kind of software |
| 40/40 | Runnable examples — example, examples, sample, samples |
Inputs used
| example_dirs | example, examples, sample, samples |
| has_mcp_signal | no |
| api_schema_files | tests/prototest/imported.proto, tests/prototest/non-positive-id.proto, tests/prototest/test.proto, tests/prototest/twice-id.proto, tests/prototest/use-reserved-id.proto |
| interfaces_expected_of | — |
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.
Key facts
0GitHub stars
99contributors
207commits, last 12 months
12days since last push
4releases
5bus factor
0open issues
Go, Maven, npm, Packagist, PyPIpackage ecosystems
Data collection warnings
- Community profile unavailable
- go package 'github.com/google/flatbuffers' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- npm package 'flatbuffers' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- packagist package 'google/flatbuffers' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- maven package 'com.google.flatbuffers:flatbuffers-java' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- pypi package 'flatbuffers' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- crates package 'flatbuffers-reflection' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- crates package 'flatbuffers' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- crates package 'flexbuffers' points at a different repository (https://github.com/google/flatbuffers); excluded from ecosystem scoring
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 5.5 / 10
5.5aggregate
Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).
| 8 | Binary-Artifacts | binaries present in source code |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 22 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 10 | Fuzzing | project is fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | no SAST tool detected |
| 10 | Security-Policy | security policy file detected |
| 10 | Signed-Releases | 4 out of the last 4 releases have a total of 4 signed artifacts. |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 0 | Vulnerabilities | 13 existing vulnerabilities detected |
Direct dependencies 16
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Maven | com.google.flatbuffers:flatbuffers-java | ${project.parent.version} | grpc/flatbuffers-java-grpc/pom.xml |
| Maven | io.grpc:grpc-core | ${gRPC.version} | grpc/flatbuffers-java-grpc/pom.xml |
| NuGet | Microsoft.SourceLink.GitHub | 8.0.0 | net/FlatBuffers/Google.FlatBuffers.csproj |
| crates.io | ahash | 0.8 | rust/flatbuffers/Cargo.toml |
| crates.io | bitflags | 2.8.0 | rust/flatbuffers/Cargo.toml |
| crates.io | ordered-float | 5 | rust/flatbuffers/Cargo.toml |
| crates.io | serde | 1.0 | rust/flatbuffers/Cargo.toml |
| crates.io | serde | 1.0.119 | rust/flexbuffers/Cargo.toml |
| crates.io | serde_derive | 1.0.119 | rust/flexbuffers/Cargo.toml |
| crates.io | byteorder | 1.4.2 | rust/flexbuffers/Cargo.toml |
| crates.io | num_enum | 0.5.1 | rust/flexbuffers/Cargo.toml |
| crates.io | bitflags | 1.2.1 | rust/flexbuffers/Cargo.toml |
| crates.io | flatbuffers | — | rust/reflection/Cargo.toml |
| crates.io | num-traits | 0.2.19 | rust/reflection/Cargo.toml |
| crates.io | anyhow | 1.0.75 | rust/reflection/Cargo.toml |
| crates.io | thiserror | 2.0 | rust/reflection/Cargo.toml |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
Raw JSON report machine-readable
Feedback
Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.
Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.
Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.29.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — Go, npm, Packagist, Maven, PyPI, crates.io.