Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 23:05 UTC

apache / skywalking-banyandb-java-client

The client implementation for SkyWalking BanyanDB in Java

JavaApache-2.0★ 21 stars⑂ 12 forkssince Aug 2021View on GitHub ↗

apache/skywalking-banyandb-java-client holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (85/100) and lowest on AI Readiness (41/100). It was last updated 173 days ago. 2 contributors account for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

23,474 followers3,145 public repossince Jan 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenorg.apache.skywalking:banyandb-java-client0.9.2-30277 days ago

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 173 days ago
5.5/36Commit cadence8/52 weeks with commits
11.1/18Commit volume16 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year16
human_commit_share
days_since_last_push173
active_weeks_last_year8
How it's scored
27/27Ships releases29 releases published
16.2/36Release recencylatest release 277 days ago
27/27Release cadencea release every ~23.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count29
latest_release_tagv0.9.2
releases_from_tagsno
days_since_latest_release277
mean_days_between_releases23.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?

51Moderate · 17% of overall
How it's scored
21.1/60Stars21 stars
8.7/25Forks12 forks
8.5/15Watchers35 watchers
Inputs used
forks12
stars21
watchers35
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingno
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?

85Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.9/22.5Commit distributiontop contributor authored 34% of commits
12.2/13.5Contributor breadth9 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled9
top_contributor_share0.336
How it's scored
0/42Issue resolutionno issues or no data
27.5/30PR acceptance97/106 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs97
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs9
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach23,474 followers of apache
25/25Track record3,145 public repos, account ~17 yr old
Inputs used
followers23,474
owner_typeOrganization
is_verified
owner_loginapache
public_repos3,145
account_age_days6,391
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on maven
26/35Publish recencylatest publish 277 days ago
20/20Version history30 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesorg.apache.skywalking:banyandb-java-client
ecosystemsmaven
any_deprecatedno
min_days_since_publish277

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests17 out of 30 merged PRs checked by a CI test -- score normalized to 5
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 sitehttps://skywalking.apache.org/
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicsskywalking, observability, apm, distributed-tracing, metrics, logging, database, time-series
has_wikino
homepagehttps://skywalking.apache.org/
docs_sitehttps://skywalking.apache.org/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.2/2.5CI-Tests17 out of 30 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 17 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
2/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities23 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.

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.

41Weak · 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
0/8Automated maintenanceno data
4/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
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_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeJava (statically typed)
55/55Manageable file sizes0/95 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes48,525
source_files_sampled95
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)src/main/proto/banyandb/v1/banyandb-common.proto, src/main/proto/banyandb/v1/banyandb-database.proto, src/main/proto/banyandb/v1/banyandb-measure.proto, src/main/proto/banyandb/v1/banyandb-model.proto, src/main/proto/banyandb/v1/banyandb-property.proto, src/main/proto/banyandb/v1/banyandb-stream.proto, src/main/proto/banyandb/v1/banyandb-trace.proto
0/20MCP servernot applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filessrc/main/proto/banyandb/v1/banyandb-common.proto, src/main/proto/banyandb/v1/banyandb-database.proto, src/main/proto/banyandb/v1/banyandb-measure.proto, src/main/proto/banyandb/v1/banyandb-model.proto, src/main/proto/banyandb/v1/banyandb-property.proto, src/main/proto/banyandb/v1/banyandb-stream.proto, src/main/proto/banyandb/v1/banyandb-trace.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

21GitHub stars
9contributors
16commits, last 12 months
173days since last push
29releases
2bus factor
0open issues
Mavenpackage ecosystems

More detail

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-07-18 23:04 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
5CI-Tests17 out of 30 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not 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
0Vulnerabilities23 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
Mavenio.grpc:grpc-netty${grpc.version}pom.xml
Mavenio.grpc:grpc-protobuf${grpc.version}pom.xml
Mavenio.grpc:grpc-stub${grpc.version}pom.xml
Mavenio.netty:netty-tcnative-boringssl-static${netty.tcnative.version}pom.xml
Mavenorg.slf4j:slf4j-api${slf4j.version}pom.xml
Mavenbuild.buf.protoc-gen-validate:protoc-gen-validate${bufbuild.protoc-gen-validate.version}pom.xml
Mavenbuild.buf.protoc-gen-validate:pgv-java-stub${bufbuild.protoc-gen-validate.version}pom.xml
Mavenio.prometheus:simpleclient${prometheus.client.version}pom.xml
All dependencies 23

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

RegistryPackageVersionRelation
Mavenbuild.buf.protoc-gen-validate:pgv-java-stub1.2.1direct
Mavenbuild.buf.protoc-gen-validate:protoc-gen-validate1.2.1direct
Mavenio.grpc:grpc-netty1.75.0direct
Mavenio.grpc:grpc-protobuf1.75.0direct
Mavenio.grpc:grpc-stub1.75.0direct
Mavenio.netty:netty-tcnative-boringssl-static2.0.65direct
Mavenio.prometheus:simpleclient0.16.0direct
Mavenorg.slf4j:slf4j-api1.7.36direct
Mavencom.google.auto.value:auto-value-annotations1.10.4indirect
Mavencom.spotify:docker-maven-plugin0.4.13indirect
Mavenio.grpc:grpc-testing1.75.0indirect
Mavenjavax.annotation:javax.annotation-api1.3.2indirect
Mavenjunit:junit4.13.2indirect
Mavenkr.motd.maven:os-maven-plugin1.7.1indirect
Mavenorg.apache.tomcat:annotations-api6.0.53indirect
Mavenorg.assertj:assertj-core3.21.0indirect
Mavenorg.awaitility:awaitility4.2.1indirect
Mavenorg.mockito:mockito-core4.8.0indirect
Mavenorg.projectlombok:lombok1.18.30indirect
Mavenorg.projectlombok:maven-compiler-plugin3.8.0indirect
Mavenorg.slf4j:slf4j-simple1.7.36indirect
Mavenorg.testcontainers:testcontainers1.19.7indirect
Mavenorg.xolstice.maven.plugins:protobuf-maven-plugin0.6.1indirect
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.14.0 — full methodology · metrics wiki.

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