Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 07:44 UTC

apache / calcite-avatica

Apache Calcite Avatica

JavaApache-2.0★ 272 stars⑂ 246 forkssince Mar 2017View on GitHub ↗
KindNetwork servicehow this is determined

apache/calcite-avatica holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Security (74/100) and lowest on Vitality (39/100). It was last updated 24 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

The Apache Software FoundationOrganization · verified domain
24,675 followers3,187 public repossince Jan 2009

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

Metrics by category

Vitality

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

39Weak · 21% of overall
How it's scored
28.8/36Push recency — last push 24 days ago
12.5/36Commit cadence — 18/52 weeks with commits
13.6/18Commit volume — 32 commits in the last year
10/10OpenSSF Scorecard: Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year32
human_commit_share0.9
days_since_last_push24
active_weeks_last_year18
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

67Good · 17% of overall
How it's scored
39.5/60Stars — 272 stars
19.9/25Forks — 246 forks
8.4/15Watchers — 33 watchers
Inputs used
forks246
stars272
watchers33
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
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com
has_pull_request_templateno

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.7/22.5Commit distribution — top contributor authored 66% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 33 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.656
How it's scored
0/42Issue resolution — no issues or no data
13/30PR acceptance — 132/305 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 9/27 approved changesets -- score normalized to 3
Inputs used
merged_prs132
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio—
closed_unmerged_prs173
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
20/20Verified domain
25/25Owner reach — 24,675 followers of apache
25/25Track record — 3,187 public repos, account ~17 yr old
Inputs used
followers24,675
owner_typeOrganization
is_verifiedyes
owner_loginapache
public_repos3,187
account_age_days6,483

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://calcite.apache.org/avatica/
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsgeospatial, calcite, java, big-data, hadoop, sql
has_wikino
homepagehttps://calcite.apache.org/avatica/
docs_sitehttps://calcite.apache.org/avatica/
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 15 out of 15 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
2.2/7.5Code-Review — Found 9/27 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 33 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages36
unassessed_packages0
affected_by_severitylow 1
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 36 resolved dependencies against OSV. 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.

63Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
3.6/40Legible commit history — 6 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.067
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes340
How it's scored
12.6/18One-command bootstrap — bom/build.gradle.kts, build.gradle.kts, core/build.gradle.kts (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 10 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsbom/build.gradle.kts, build.gradle.kts, core/build.gradle.kts, metrics-dropwizardmetrics/build.gradle.kts, metrics/build.gradle.kts, noop-driver/build.gradle.kts, release/build.gradle.kts, server/build.gradle.kts, shaded/core/build.gradle.kts, standalone-server/build.gradle.kts, tck/build.gradle.kts
dependency_bot_commit_share0.1
How it's scored
45/45Type-checkable code — Java (statically typed)
54.1/55Manageable file sizes — 5/318 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes111,319
source_files_sampled318
oversized_source_files5
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — core/src/main/protobuf/common.proto, core/src/main/protobuf/requests.proto, core/src/main/protobuf/responses.proto
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filescore/src/main/protobuf/common.proto, core/src/main/protobuf/requests.proto, core/src/main/protobuf/responses.proto
interfaces_expected_ofnetwork-service

Key facts

272GitHub stars
99contributors
32commits, last 12 months
24days since last push
0releases
1bus factor
0open issues
Maven, RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 246 ⇿
0Stars
246Forks

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.

0408012016020024022942017-032021-122026-09

Each point covers 9 days.

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-10-19 07:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 9/27 approved changesets -- score normalized to 3
10Contributorsproject has 33 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained16 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
RubyGemsjekyll~>4site/Gemfile
RubyGemswebrick~> 1.9.1site/Gemfile
RubyGemsjekyll-redirect-from—site/Gemfile
All dependencies 36

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

RegistryPackageVersionRelation
RubyGemsjekyll4.4.1direct
RubyGemsjekyll-redirect-from0.16.0direct
RubyGemswebrick1.9.2direct
RubyGemsaddressable2.9.0indirect
RubyGemsbase640.2.0indirect
RubyGemsbigdecimal3.1.8indirect
RubyGemscolorator1.1.0indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemscsv3.3.2indirect
RubyGemsem-websocket0.5.3indirect
RubyGemseventmachine1.2.7indirect
RubyGemsffi1.17.4indirect
RubyGemsforwardable-extended2.6.0indirect
RubyGemsgoogle-protobuf4.36.1indirect
RubyGemshttp_parser.rb0.8.1indirect
RubyGemsi18n1.15.2indirect
RubyGemsjekyll-sass-converter3.1.0indirect
RubyGemsjekyll-watch2.2.1indirect
RubyGemsjson2.9.1indirect
RubyGemskramdown2.5.2indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemsliquid4.0.4indirect
RubyGemslisten3.10.0indirect
RubyGemslogger1.6.4indirect
RubyGemsmercenary0.4.0indirect
RubyGemspathutil0.16.2indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsrake13.4.2indirect
RubyGemsrb-fsevent0.11.2indirect
RubyGemsrb-inotify0.11.1indirect
RubyGemsrexml3.4.4indirect
RubyGemsrouge4.7.0indirect
RubyGemssafe_yaml1.0.5indirect
RubyGemssass-embedded1.104.0indirect
RubyGemsterminal-table3.0.2indirect
RubyGemsunicode-display_width2.6.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 36 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
json2.9.1indirectlow12.19.9

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.