Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 13:25 UTC

vert-x3 / vertx-grpc

gRPC for Vert.x

JavaNo license detected★ 84 stars⑂ 44 forkssince Feb 2017View on GitHub ↗

vert-x3/vertx-grpc holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (68/100) and lowest on AI Readiness (51/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Eclipse Vert.xOrganization
340 followers92 public repossince Jul 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenio.vertx:vertx-grpc5.1.8-1643 days ago
Mavenio.vertx:vertx-grpc-protoc-plugin5.1.8-1163 days ago

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
6.2/36Commit cadence — 9/52 weeks with commits
11.7/18Commit volume — 19 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year19
human_commit_share1
days_since_last_push3
active_weeks_last_year9
How it's scored
16.2/27Ships releases — 93 version tags (no GitHub releases)
36/36Release recency — latest release 3 days ago
27/27Release cadence — a release every ~14.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count93
latest_release_tag5.1.8
releases_from_tagsyes
days_since_latest_release3
mean_days_between_releases14.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?

52Moderate · 17% of overall
How it's scored
31.1/60Stars — 84 stars
13.6/25Forks — 44 forks
7.4/15Watchers — 22 watchers
Inputs used
forks44
stars84
watchers22
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges—
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.3/22.5Commit distribution — top contributor authored 67% of commits
13.5/13.5Contributor breadth — 19 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.674
How it's scored
34/42Issue resolution — 81% of issues closed
20.2/30PR acceptance — 58/86 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs58
open_issues13
closed_issues55
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.809
closed_unmerged_prs28
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
18.2/25Owner reach — 340 followers of vert-x3
25/25Track record — 92 public repos, account ~12 yr old
Inputs used
followers340
owner_typeOrganization
is_verifiedno
owner_loginvert-x3
public_repos92
account_age_days4,448

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on maven
35/35Publish recency — latest publish 3 days ago
20/20Version history — 164 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesio.vertx:vertx-grpc, io.vertx:vertx-grpc-protoc-plugin
ecosystemsmaven
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 2 out of 2 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsvertx, grpc, java, reactive, http2
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?

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 2 out of 2 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
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 12 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
10/25Indirect dependencies free of known advisories — 1 affected: com.google.protobuf:protobuf-java 3.25.1 (high 7.5)
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 723 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages40
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the maven:io.vertx:vertx-grpc@5.1.8 runtime dependency closure — what installing the published package pulls in — 40 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.

51Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.2/40Legible commit history — 6 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.06
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — pom.xml, vertx-grpc-protoc-plugin/pom.xml, vertx-grpc/pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestspom.xml, vertx-grpc-protoc-plugin/pom.xml, vertx-grpc/pom.xml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Java (statically typed)
55/55Manageable file sizes — 0/29 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes17,517
source_files_sampled29
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — vertx-grpc/src/main/proto/helloworld.proto, vertx-grpc/src/test/proto/empty.proto, vertx-grpc/src/test/proto/helloworld.proto, vertx-grpc/src/test/proto/messages.proto, vertx-grpc/src/test/proto/optionals.proto, vertx-grpc/src/test/proto/streaming.proto, vertx-grpc/src/test/proto/test.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesvertx-grpc/src/main/proto/helloworld.proto, vertx-grpc/src/test/proto/empty.proto, vertx-grpc/src/test/proto/helloworld.proto, vertx-grpc/src/test/proto/messages.proto, vertx-grpc/src/test/proto/optionals.proto, vertx-grpc/src/test/proto/streaming.proto, vertx-grpc/src/test/proto/test.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

84GitHub stars
19contributors
19commits, last 12 months
3days since last push
93releases
1bus factor
13open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 44 ⇿
0Stars
44Forks
48Releases

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.

010203040504422017-042021-022024-11
Major 0Minor 3Patch 45

Each point covers 7 days.

OpenSSF Scorecard 4.5 / 10
4.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).Scorecard v5.5.0 · 2026-09-13 13:24 UTC

10Binary-Artifactsno binaries found in the repo
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-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
Mavenio.vertx:vertx-dependencies${project.version}pom.xml
Mavenio.vertx:vertx-codegen-api—pom.xml
Mavenio.vertx:vertx-codegen-json—pom.xml
Mavenio.vertx:vertx-docgen-api—pom.xml
Mavencom.salesforce.servicelibs:jprotoc${jprotoc.version}vertx-grpc-protoc-plugin/pom.xml
Mavenio.vertx:vertx-core—vertx-grpc/pom.xml
Mavenio.grpc:grpc-netty${grpc.version}vertx-grpc/pom.xml
Mavenio.grpc:grpc-protobuf${grpc.version}vertx-grpc/pom.xml
Mavenio.grpc:grpc-stub${grpc.version}vertx-grpc/pom.xml
Mavenjavax.annotation:javax.annotation-api1.3.2vertx-grpc/pom.xml
Mavencom.google.guava:guava—vertx-grpc/pom.xml
Mavenio.vertx:vertx-grpc-protoc-plugin${project.version}vertx-grpc/pom.xml
All dependencies 24

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

RegistryPackageVersionRelation
Mavencom.google.guava:guava—direct
Mavencom.salesforce.servicelibs:jprotoc1.2.1direct
Mavenio.grpc:grpc-netty1.65.0direct
Mavenio.grpc:grpc-protobuf1.65.0direct
Mavenio.grpc:grpc-stub1.65.0direct
Mavenio.vertx:vertx-codegen-api—direct
Mavenio.vertx:vertx-codegen-json—direct
Mavenio.vertx:vertx-core—direct
Mavenio.vertx:vertx-dependencies5.2.0-SNAPSHOTdirect
Mavenio.vertx:vertx-docgen-api—direct
Mavenio.vertx:vertx-grpc-protoc-plugin5.2.0-SNAPSHOTdirect
Mavenjavax.annotation:javax.annotation-api1.3.2direct
Mavencom.diffplug.spotless:spotless-maven-plugin—indirect
Mavencom.salesforce.servicelibs:canteen-maven-plugin1.1.0indirect
Mavenio.netty:netty-resolver-dns-native-macos—indirect
Mavenio.netty:netty-transport-native-epoll—indirect
Mavenio.netty:netty-transport-native-io_uring—indirect
Mavenio.netty:netty-transport-native-kqueue—indirect
Mavenio.vertx:maven-compiler-plugin—indirect
Mavenio.vertx:vertx-unit—indirect
Mavenjunit:junit4.13.2indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin—indirect
Mavenorg.apache.maven.plugins:maven-shade-plugin3.2.1indirect
Mavenorg.xolstice.maven.plugins:protobuf-maven-plugin0.6.1indirect
Dependency advisories 1

Installing maven:io.vertx:vertx-grpc@5.1.8 pulls in 40 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
com.google.protobuf:protobuf-java3.25.1indirecthigh14.28.2

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