Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 14:07 UTC

elixir-grpc / grpc

An Elixir implementation of gRPC

ElixirApache-2.0★ 1,524 stars⑂ 264 forkssince Jul 2016View on GitHub ↗

elixir-grpc/grpc holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (85/100) and lowest on Security (46/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

elixir-grpcOrganization
12 followers8 public repossince Mar 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexgrpc1.0.5259,1893019 days ago
Hexgrpc_core1.0.537,563919 days ago
Hexgrpc_server1.0.517,791719 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
23.5/36Commit cadence — 34/52 weeks with commits
17.9/18Commit volume — 97 commits in the last year
10/10OpenSSF Scorecard: Maintained — 28 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year97
human_commit_share1
days_since_last_push10
active_weeks_last_year34
How it's scored
27/27Ships releases — 18 releases published
36/36Release recency — latest release 19 days ago
19.8/27Release cadence — a release every ~46.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tagv1.0.5
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases46.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

72Good · 17% of overall
How it's scored
51.6/60Stars — 1,524 stars
20.2/25Forks — 264 forks
7.8/15Watchers — 26 watchers
Inputs used
forks264
stars1,524
watchers26
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
73.3/80Monthly downloads — 314,543 downloads/month across hex
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgrpc, grpc_core, grpc_server
dependents—
ecosystemshex
total_downloads7,130,406
monthly_downloads314,543
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.5/22.5Commit distribution — top contributor authored 53% of commits
13.5/13.5Contributor breadth — 89 contributors
10/10OpenSSF Scorecard: Contributors — project has 33 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled89
top_contributor_share0.534
How it's scored
35.3/42Issue resolution — 84% of issues closed
23.2/30PR acceptance — 260/336 decided PRs merged
10.4/13Newcomer PR acceptance — 4/5 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 21/30 approved changesets -- score normalized to 7
Inputs used
merged_prs260
open_issues39
closed_issues207
prs_merged_7d0
prs_decided_7d0
prs_merged_30d7
prs_decided_30d8
issue_closed_ratio0.841
closed_unmerged_prs76
first_time_authors_30d4
first_time_prs_merged_30d4
first_time_prs_decided_30d5
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
8/25Owner reach — 12 followers of elixir-grpc
18.9/25Track record — 8 public repos, account ~7 yr old
Inputs used
followers12
owner_typeOrganization
is_verifiedno
owner_loginelixir-grpc
public_repos8
account_age_days2,742

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on hex
35/35Publish recency — latest publish 19 days ago
20/20Version history — 30 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgrpc, grpc_core, grpc_server
ecosystemshex
any_deprecatedno
min_days_since_publish19

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 27 out of 27 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://hex.pm/packages/grpc
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsgrpc, elixir, grpc-elixir, rpc, http2, protobuf, google-protocol-buffers, proto
has_wikiyes
homepagehttps://hex.pm/packages/grpc
docs_sitehttps://hex.pm/packages/grpc
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
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 21/30 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 33 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 28 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 22 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 94 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.94
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — benchmark/Makefile, interop/Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesmix.lock
has_dockerfileyes
typed_languageno
bootstrap_filesbenchmark/Makefile, interop/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.03
toolchain_manifestsbenchmark/mix.exs, grpc/mix.exs, grpc_core/mix.exs, grpc_server/mix.exs, interop/mix.exs, mix.exs
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Elixir without a type-check config
55/55Manageable file sizes — 0/213 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes49,496
source_files_sampled213
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — benchmark/proto/core/stats.proto, benchmark/proto/testing/benchmark_service.proto, benchmark/proto/testing/control.proto, benchmark/proto/testing/messages.proto, benchmark/proto/testing/payloads.proto, benchmark/proto/testing/stats.proto, benchmark/proto/testing/worker_service.proto, grpc/test/support/proto/collision_test.proto, grpc/test/support/proto/helloworld.proto, grpc/test/support/proto/route_guide.proto, grpc/test/support/transcode_messages.proto, grpc_server/test/support/google/api/annotations.proto, grpc_server/test/support/google/api/http.proto, grpc_server/test/support/google/protobuf/descriptor.proto, grpc_server/test/support/proto/helloworld.proto, grpc_server/test/support/proto/route_guide.proto, grpc_server/test/support/transcode_messages.proto
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesbenchmark/proto/core/stats.proto, benchmark/proto/testing/benchmark_service.proto, benchmark/proto/testing/control.proto, benchmark/proto/testing/messages.proto, benchmark/proto/testing/payloads.proto, benchmark/proto/testing/stats.proto, benchmark/proto/testing/worker_service.proto, grpc/test/support/proto/collision_test.proto, grpc/test/support/proto/helloworld.proto, grpc/test/support/proto/route_guide.proto, grpc/test/support/transcode_messages.proto, grpc_server/test/support/google/api/annotations.proto, grpc_server/test/support/google/api/http.proto, grpc_server/test/support/google/protobuf/descriptor.proto, grpc_server/test/support/proto/helloworld.proto, grpc_server/test/support/proto/route_guide.proto, grpc_server/test/support/transcode_messages.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

1,524GitHub stars
89contributors
97commits, last 12 months
10days since last push
18releases
1bus factor
39open issues
Hexpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch hex package 'grpc_root' from its registry
  • Could not fetch hex package 'interop' from its registry

More detail

Star and fork history 0 ★ / 264 ⇿
0Stars
264Forks
17Releases

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.

05010015020025024842016-102021-092026-08
Major 1Minor 7Patch 9

Each point covers 10 days.

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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).Scorecard v5.5.0 · 2026-09-19 14:07 UTC

9Binary-Artifactsbinaries present in source code
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 21/30 approved changesets -- score normalized to 7
10Contributorsproject has 33 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities22 existing vulnerabilities detected
Direct dependencies 25
RegistryPackageVersion constraintManifest
Hexgrpc_core../grpc_coregrpc/mix.exs
Hexgrpc_core~> 1.0.5grpc/mix.exs
Hexgun~> 2.4.0grpc/mix.exs
Hexmint~> 1.9grpc/mix.exs
Hexcastore~> 1.0grpc/mix.exs
Hexprotobuf~> 0.17grpc_core/mix.exs
Hexjason>= 0.0.0grpc_core/mix.exs
Hextelemetry~> 1.0grpc_core/mix.exs
Hexgoogleapis~> 0.1.0grpc_core/mix.exs
Hexgrpc_core../grpc_coregrpc_server/mix.exs
Hexgrpc_core~> 1.0.5grpc_server/mix.exs
Hexprotobuf~> 0.17grpc_server/mix.exs
Hexcowboy~> 2.14grpc_server/mix.exs
Hexcowlib~> 2.14grpc_server/mix.exs
Hexflow~> 1.2grpc_server/mix.exs
Hexgrpc_server../grpc_serverinterop/mix.exs
Hexgrpc../grpcinterop/mix.exs
Hexprotobuf~> 0.17interop/mix.exs
Hexgun~> 2.0interop/mix.exs
Hexmint~> 1.5interop/mix.exs
Hexgrpc_statsd~> 0.1.0interop/mix.exs
Hexstatix>= 1.2.1interop/mix.exs
Hexextrace~> 0.2interop/mix.exs
Hexgrpc_servergrpc_servermix.exs
Hexshutdown—mix.exs
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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 — Hex.