Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 17:31 UTC

eclipse-vertx / vertx-auth

Authentication and authorization providers for Eclipse Vert.x

JavaApache-2.0★ 174 stars⑂ 158 forkssince Dec 2014View on GitHub ↗

eclipse-vertx/vertx-auth holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (76/100) and lowest on AI Readiness (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Eclipse Vert.xOrganization
252 followers20 public repossince Jun 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenio.vertx:vertx-auth-parent5.1.5-690 days ago
Mavenio.vertx:vertx-auth-abac5.1.5-277 days ago
Mavenio.vertx:vertx-auth-common5.1.5-1700 days ago
Mavenio.vertx:vertx-auth-htdigest5.1.5-1590 days ago
Mavenio.vertx:vertx-auth-htpasswd5.1.5-1550 days ago
Mavenio.vertx:vertx-auth-jwt5.1.5-1700 days ago
Mavenio.vertx:vertx-auth-ldap5.1.5-1110 days ago
Mavenio.vertx:vertx-auth-oauth25.1.5-1670 days ago

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9/36Commit cadence13/52 weeks with commits
12.7/18Commit volume25 commits in the last year
10/10OpenSSF Scorecard: Maintained11 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year25
human_commit_share
days_since_last_push0
active_weeks_last_year13
How it's scored
16.2/27Ships releases89 version tags (no GitHub releases)
36/36Release recencylatest release 7 days ago
27/27Release cadencea release every ~12.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count89
latest_release_tag5.1.5
releases_from_tagsyes
days_since_latest_release7
mean_days_between_releases12.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?

73Good · 17% of overall
How it's scored
36.3/60Stars174 stars
18.3/25Forks158 forks
8.2/15Watchers31 watchers
Inputs used
forks158
stars174
watchers31
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateyes
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?

72Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.6/22.5Commit distributiontop contributor authored 57% of commits
13.5/13.5Contributor breadth70 contributors
10/10OpenSSF Scorecard: Contributorsproject has 29 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled70
top_contributor_share0.572
How it's scored
38.2/42Issue resolution91% of issues closed
23.6/30PR acceptance312/397 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/29 approved changesets -- score normalized to 1
Inputs used
merged_prs312
open_issues31
closed_issues309
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.909
closed_unmerged_prs85
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
17.3/25Owner reach252 followers of eclipse-vertx
21.6/25Track record20 public repos, account ~10 yr old
Inputs used
followers252
owner_typeOrganization
is_verified
owner_logineclipse-vertx
public_repos20
account_age_days3,694
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable8 package(s) on maven
35/35Publish recencylatest publish 0 days ago
20/20Version history170 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesio.vertx:vertx-auth-parent, io.vertx:vertx-auth-abac, io.vertx:vertx-auth-common, io.vertx:vertx-auth-htdigest, io.vertx:vertx-auth-htpasswd, io.vertx:vertx-auth-jwt, io.vertx:vertx-auth-ldap, io.vertx:vertx-auth-oauth2
ecosystemsmaven
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests8 out of 9 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://vertx.io/docs/vertx-auth-common/java/
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicssecurity, oauth, oauth2, jwt, vertx, async, reactive
has_wikino
homepagehttps://vertx.io/docs/vertx-auth-common/java/
docs_sitehttps://vertx.io/docs/vertx-auth-common/java/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests8 out of 9 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 4/29 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 29 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained11 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4.5/5SASTSAST tool detected but not run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages14
unassessed_packages15
affected_by_severityhigh 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 14 resolved dependencies against OSV. 15 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingJava (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeJava (statically typed)
54.8/55Manageable file sizes1/293 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes81,116
source_files_sampled293
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

174GitHub stars
70contributors
25commits, last 12 months
0days since last push
89releases
1bus factor
31open issues
Mavenpackage ecosystems

Data collection warnings

  • deps.dev does not index maven:io.vertx:vertx-auth-parent@5.1.5; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 6.6 / 10
6.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-07-20 17:30 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
8CI-Tests8 out of 9 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/29 approved changesets -- score normalized to 1
10Contributorsproject has 29 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained11 commit(s) and 2 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
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
Mavenio.vertx:vertx-dependencies${project.version}pom.xml
Mavenio.vertx:vertx-codegen-apipom.xml
Mavenio.vertx:vertx-codegen-jsonpom.xml
Mavenio.vertx:vertx-docgen-apipom.xml
Mavenio.vertx:vertx-corepom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-abac/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-htdigest/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-htpasswd/pom.xml
Mavencommons-codec:commons-codec1.15vertx-auth-htpasswd/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-jwt/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-ldap/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-oauth2/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-otp/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-properties/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-sql-client/pom.xml
Mavenio.vertx:vertx-sql-clientvertx-auth-sql-client/pom.xml
Mavenio.vertx:vertx-auth-commonvertx-auth-webauthn4j/pom.xml
Mavencom.webauthn4j:webauthn4j-core-async${webauthn4j.version}vertx-auth-webauthn4j/pom.xml
Mavencom.webauthn4j:webauthn4j-metadata-async${webauthn4j.version}vertx-auth-webauthn4j/pom.xml
All dependencies 29

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

RegistryPackageVersionRelation
Mavencom.webauthn4j:webauthn4j-core-async0.30.3.RELEASEdirect
Mavencom.webauthn4j:webauthn4j-metadata-async0.30.3.RELEASEdirect
Mavencommons-codec:commons-codec1.15direct
Mavenio.vertx:vertx-auth-commondirect
Mavenio.vertx:vertx-codegen-apidirect
Mavenio.vertx:vertx-codegen-jsondirect
Mavenio.vertx:vertx-coredirect
Mavenio.vertx:vertx-dependencies5.2.0-SNAPSHOTdirect
Mavenio.vertx:vertx-docgen-apidirect
Mavenio.vertx:vertx-sql-clientdirect
Mavencom.webauthn4j:webauthn4j-test0.30.3.RELEASEindirect
Mavenio.agroal:agroal-api1.12indirect
Mavenio.agroal:agroal-pool1.12indirect
Mavenio.vertx:maven-compiler-pluginindirect
Mavenio.vertx:vertx-auth-jwtindirect
Mavenio.vertx:vertx-jdbc-clientindirect
Mavenio.vertx:vertx-mysql-clientindirect
Mavenio.vertx:vertx-unitindirect
Mavenjunit:junit4.13.2indirect
Mavenmysql:mysql-connector-java8.0.30indirect
Mavenorg.apache.directory.server:apacheds-test-framework2.0.0.AM25indirect
Mavenorg.apache.maven.plugins:maven-failsafe-plugin3.0.0indirect
Mavenorg.codehaus.mojo:build-helper-maven-pluginindirect
Mavenorg.testcontainers:testcontainersindirect
Mavenorg.testcontainers:testcontainers1.21.4indirect
npmjsonwebtoken7.4.1indirect
npmmocha3.4.2indirect
npmnode-jose*indirect
npmpem*indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 14 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct. 15 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
jsonwebtoken7.4.1indirecthigh39.0.0
mysql:mysql-connector-java8.0.30indirecthigh18.2.0

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

How one result sits in the wider record: aggregate statisticsMaven.