Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 04:09 UTC

opencord / voltha-protos

Multi-language protobuf definitions and packaging for VOLTHA

Go · MakefileApache-2.0★ 9 stars⑂ 11 forkssince Mar 2019View on GitHub ↗

opencord/voltha-protos holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Engineering Quality (71/100) and lowest on Security (46/100). It was last updated 61 days ago. 7 contributors account for most of its recent work.

65
overall / 100
Good

Software 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.

65
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)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

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 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).

Ownership

CORDOrganization
67 followers154 public repossince Apr 2016

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Gogithub.com/opencord/voltha-protos/v5v5.7.10-4895 days ago—
PyPIvoltha-protospoints to another repo — not scored5.7.109111289 days agoprotobufvoltha

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

58Moderate · 21% of overall
How it's scored
18/36Push recency — last push 61 days ago
10.4/36Commit cadence — 15/52 weeks with commits
12.2/18Commit volume — 22 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year22
human_commit_share1
days_since_last_push61
active_weeks_last_year15
How it's scored
16.2/27Ships releases — 99 version tags (no GitHub releases)
27/36Release recency — latest release 95 days ago
27/27Release cadence — a release every ~20.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count99
latest_release_tagv5.7.10
releases_from_tagsyes
days_since_latest_release95
mean_days_between_releases20.3

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

53Moderate · 17% of overall
How it's scored
14.6/60Stars — 9 stars
8.3/25Forks — 11 forks
1.7/15Watchers — 3 watchers
Inputs used
forks11
stars9
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

68Good · 23% of overall
How it's scored
51.3/54Bus factor — 7 contributor(s) cover half of all commits
19.2/22.5Commit distribution — top contributor authored 15% of commits
13.5/13.5Contributor breadth — 37 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor7
contributors_sampled37
top_contributor_share0.146
How it's scored
0/42Issue resolution — no issues or no data
3.3/30PR acceptance — 1/9 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs8
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
13.2/25Owner reach — 67 followers of opencord
25/25Track record — 154 public repos, account ~10 yr old
Inputs used
followers67
owner_typeOrganization
is_verifiedno
owner_loginopencord
public_repos154
account_age_days3,861

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 95 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/opencord/voltha-protos/v5
ecosystemsgo
any_deprecatedno
min_days_since_publish95

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — tox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

46Weak · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesgo.sum
manifestsgo.mod, requirements.txt, setup.py, test/pom.xml
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages6
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:voltha-protos@5.7.10 runtime dependency closure — what installing the published package pulls in — 6 packages. Reachability is not analyzed.

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.

66Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
37.9/40Legible commit history — 71 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.71
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile, vendor/google.golang.org/grpc/Makefile
22/22Automated tests
11/11Lint / format config — tox.ini
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, vendor/google.golang.org/grpc/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo.mod, test/pom.xml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
40.9/55Manageable file sizes — 10/39 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes410,825
source_files_sampled39
oversized_source_files10
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — protos/google/api/annotations.proto, protos/google/api/http.proto, protos/voltha_protos/adapter.proto, protos/voltha_protos/adapter_service.proto, protos/voltha_protos/common.proto, protos/voltha_protos/core.proto, protos/voltha_protos/core_adapter.proto, protos/voltha_protos/core_services.proto, protos/voltha_protos/device.proto, protos/voltha_protos/events.proto, protos/voltha_protos/ext_config.proto, protos/voltha_protos/extensions.proto, protos/voltha_protos/health.proto, protos/voltha_protos/ietf_interfaces.proto, protos/voltha_protos/inter_adapter.proto, protos/voltha_protos/logical_device.proto, protos/voltha_protos/olt_inter_adapter_service.proto, protos/voltha_protos/omci_alarm_db.proto, protos/voltha_protos/omci_mib_db.proto, protos/voltha_protos/omci_test.proto, protos/voltha_protos/onu_inter_adapter_service.proto, protos/voltha_protos/openflow_13.proto, protos/voltha_protos/openolt.proto, protos/voltha_protos/tech_profile.proto, protos/voltha_protos/voip_system_profile.proto, protos/voltha_protos/voip_user_profile.proto, protos/voltha_protos/voltha.proto
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesprotos/google/api/annotations.proto, protos/google/api/http.proto, protos/voltha_protos/adapter.proto, protos/voltha_protos/adapter_service.proto, protos/voltha_protos/common.proto, protos/voltha_protos/core.proto, protos/voltha_protos/core_adapter.proto, protos/voltha_protos/core_services.proto, protos/voltha_protos/device.proto, protos/voltha_protos/events.proto, protos/voltha_protos/ext_config.proto, protos/voltha_protos/extensions.proto, protos/voltha_protos/health.proto, protos/voltha_protos/ietf_interfaces.proto, protos/voltha_protos/inter_adapter.proto, protos/voltha_protos/logical_device.proto, protos/voltha_protos/olt_inter_adapter_service.proto, protos/voltha_protos/omci_alarm_db.proto, protos/voltha_protos/omci_mib_db.proto, protos/voltha_protos/omci_test.proto, protos/voltha_protos/onu_inter_adapter_service.proto, protos/voltha_protos/openflow_13.proto, protos/voltha_protos/openolt.proto, protos/voltha_protos/tech_profile.proto, protos/voltha_protos/voip_system_profile.proto, protos/voltha_protos/voip_user_profile.proto, protos/voltha_protos/voltha.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

9GitHub stars
37contributors
22commits, last 12 months
61days since last push
99releases
7bus factor
0open issues
Go, Maven, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi package 'voltha-protos' points at a different repository (https://gerrit.opencord.org/gitweb?p=voltha-protos.git); excluded from ecosystem scoring
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 11 ⇿
0Stars
11Forks
92Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0246810121112019-042022-122026-07
Major 2Minor 11Patch 78

Each point covers 7 days.

Direct dependencies 3
RegistryPackageVersion constraintManifest
Gogoogle.golang.org/genproto/googleapis/apiv0.0.0-20251213004720-97cd9d5aeac2go.mod
Gogoogle.golang.org/grpcv1.77.0go.mod
Gogoogle.golang.org/protobufv1.36.11go.mod
All dependencies 15

Full resolved dependency set from the GitHub dependency graph: 3 direct and 12 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Gogoogle.golang.org/genproto/googleapis/apiv0.0.0-20251213004720-97cd9d5aeac2direct
Gogoogle.golang.org/grpcv1.77.0direct
Gogoogle.golang.org/protobufv1.36.11direct
Gogolang.org/x/netv0.46.1-0.20251013234738-63d1a5100f82indirect
Gogolang.org/x/sysv0.37.0indirect
Gogolang.org/x/textv0.30.0indirect
Gogoogle.golang.org/genproto/googleapis/rpcv0.0.0-20251124214823-79d6a2a48846indirect
Mavencom.google.api.grpc:proto-google-common-protos2.68.0indirect
Mavencom.google.protobuf:protobuf-java4.32.1indirect
PyPIgoogleapis-common-protos—indirect
PyPIgrpcio—indirect
PyPIgrpcio-tools—indirect
PyPInose2—indirect
PyPIprotobuf—indirect
PyPItox—indirect
Dependency advisories 0

Installing pypi:voltha-protos@5.7.10 pulls in 6 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.

The message is kept through sign-in.

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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Go, PyPI.