Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-02 01:26 UTC

apache / horaedb

Apache HoraeDB (incubating) is a high-performance, distributed, cloud native time-series database.

RustApache-2.0★ 2,828 stars⑂ 221 forkssince May 2022archivedView on GitHub ↗
KindNetwork serviceLibraryCommand-line toolhow this is determined

apache/horaedb holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Community & Adoption (88/100) and lowest on Vitality (30/100). The repository is archived, so no further maintenance is expected.

19
overall / 100
Critical

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.

19
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

The Apache Software FoundationOrganization · verified domain
24,071 followers3,165 public repossince Jan 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iocommon0.1.011612651 days ago
crates.ioserverpoints to another repo — not scored0.0.0421570 days agowebserverlocalnetwork-programmingweb-programming

Metrics by category

Vitality

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

30At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 208 days ago
1.4/36Commit cadence2/52 weeks with commits
5.4/18Commit volume3 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year3
human_commit_share0.93
days_since_last_push208
active_weeks_last_year2
How it's scored
27/27Ships releases16 releases published
7.2/36Release recencylatest release 652 days ago
19.8/27Release cadencea release every ~66.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count16
latest_release_tagv2.1.0
releases_from_tagsno
days_since_latest_release652
mean_days_between_releases66.5
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?

88Excellent · 17% of overall
How it's scored
56/60Stars2,828 stars
19.5/25Forks221 forks
8.9/15Watchers41 watchers
Inputs used
forks221
stars2,828
watchers41
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

82Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
17.5/22.5Commit distributiontop contributor authored 22% of commits
13.5/13.5Contributor breadth43 contributors
10/10OpenSSF Scorecard: Contributorsproject has 14 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled43
top_contributor_share0.222
How it's scored
40.1/42Issue resolution95% of issues closed
27.3/30PR acceptance1,058/1,161 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_prs1,058
open_issues21
closed_issues432
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.954
closed_unmerged_prs103
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 backingorganization-owned
20/20Verified domain
25/25Owner reach24,071 followers of apache
25/25Track record3,165 public repos, account ~17 yr old
Inputs used
followers24,071
owner_typeOrganization
is_verifiedyes
owner_loginapache
public_repos3,165
account_age_days6,436
How it's scored
25/25Published & resolvable1 package(s) on crates
4/35Publish recencylatest publish 2,651 days ago
4/20Version history1 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescommon
ecosystemscrates
any_deprecatedno
min_days_since_publish2,651

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configclippy.toml, rustfmt.toml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests3 out of 22 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://horaedb.apache.org
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsdistributed-database, rust, tsdb, cloud-native, iot-database, timeseries-analysis, timeseries-database, horaedb, prometheus-remote-storage
has_wikiyes
homepagehttps://horaedb.apache.org
docs_sitehttps://horaedb.apache.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests3 out of 22 merged PRs checked by a CI test -- score normalized to 1
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 14 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
0/7.5Maintainedproject is archived
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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.5Vulnerabilities18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
26.6/35Direct dependencies free of known advisories1 affected: bincode 1.3.3 (unknown)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
37.2/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 259 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages10
unassessed_packages0
affected_by_severityunknown 1
direct_affected_packages1
Matched the crates:common@0.1.0 runtime dependency closure — what installing the published package pulls in — 10 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.

65Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history84 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.903
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configclippy.toml, rustfmt.toml
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance7 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, src/benchmarks/Cargo.toml, src/columnar_storage/Cargo.toml, src/common/Cargo.toml, src/metric_engine/Cargo.toml, src/pb_types/Cargo.toml, src/remote_write/Cargo.toml, src/server/Cargo.toml
dependency_bot_commit_share0.07
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/44 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes21,308
source_files_sampled44
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)src/pb_types/protos/remote_write.proto, src/pb_types/protos/sst.proto
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filessrc/pb_types/protos/remote_write.proto, src/pb_types/protos/sst.proto
interfaces_expected_ofnetwork-service

Key facts

2,828GitHub stars
43contributors
3commits, last 12 months
208days since last push
16releases
3bus factor
21open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'server' points at a different repository (https://github.com/reu/server); excluded from ecosystem scoring
  • Could not fetch crates package 'pb_types' from its registry
  • Could not fetch crates package 'remote_write' from its registry
  • Could not fetch crates package 'metric_engine' from its registry
  • Could not fetch crates package 'columnar_storage' from its registry

More detail

Star and fork history 0 ★ / 221 ⇿
0Stars
221Forks
16Releases

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.

4080120160200240209492022-062024-072026-08
Major 2Minor 6Patch 5

Each point covers 4 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-02 01:25 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
1CI-Tests3 out of 22 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 14 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 49
RegistryPackageVersion constraintManifest
crates.ioanyhowsrc/columnar_storage/Cargo.toml
crates.ioarrowsrc/columnar_storage/Cargo.toml
crates.ioasync-scopedsrc/columnar_storage/Cargo.toml
crates.ioasync-traitsrc/columnar_storage/Cargo.toml
crates.iobyteordersrc/columnar_storage/Cargo.toml
crates.iobytessrc/columnar_storage/Cargo.toml
crates.iocommonsrc/columnar_storage/Cargo.toml
crates.iodatafusionsrc/columnar_storage/Cargo.toml
crates.iofuturessrc/columnar_storage/Cargo.toml
crates.ioitertoolssrc/columnar_storage/Cargo.toml
crates.iolazy_staticsrc/columnar_storage/Cargo.toml
crates.ioobject_storesrc/columnar_storage/Cargo.toml
crates.ioparquetsrc/columnar_storage/Cargo.toml
crates.iopb_typessrc/columnar_storage/Cargo.toml
crates.ioprostsrc/columnar_storage/Cargo.toml
crates.ioserdesrc/columnar_storage/Cargo.toml
crates.iotokiosrc/columnar_storage/Cargo.toml
crates.iotracingsrc/columnar_storage/Cargo.toml
crates.ioanyhowsrc/common/Cargo.toml
crates.ioserdesrc/common/Cargo.toml
crates.iothiserrorsrc/common/Cargo.toml
crates.iotomlsrc/common/Cargo.toml
crates.ioanyhowsrc/metric_engine/Cargo.toml
crates.iocolumnar_storagesrc/metric_engine/Cargo.toml
crates.iocommonsrc/metric_engine/Cargo.toml
crates.ioseahashsrc/metric_engine/Cargo.toml
crates.iothiserrorsrc/metric_engine/Cargo.toml
crates.iotokiosrc/metric_engine/Cargo.toml
crates.iotracingsrc/metric_engine/Cargo.toml
crates.ioprostsrc/pb_types/Cargo.toml
crates.ioanyhowsrc/remote_write/Cargo.toml
crates.iobytessrc/remote_write/Cargo.toml
crates.ioobject-poolsrc/remote_write/Cargo.toml
crates.ioonce_cellsrc/remote_write/Cargo.toml
crates.iopb_typessrc/remote_write/Cargo.toml
crates.ioprostsrc/remote_write/Cargo.toml
crates.ioactix-web4src/server/Cargo.toml
crates.ioarrowsrc/server/Cargo.toml
crates.ioclapsrc/server/Cargo.toml
crates.iocolumnar_storagesrc/server/Cargo.toml
crates.iocommonsrc/server/Cargo.toml
crates.iofuturessrc/server/Cargo.toml
crates.ioobject_storesrc/server/Cargo.toml
crates.iorand0.8src/server/Cargo.toml
crates.ioserdesrc/server/Cargo.toml
crates.iotokiosrc/server/Cargo.toml
crates.iotomlsrc/server/Cargo.toml
crates.iotracingsrc/server/Cargo.toml
crates.iotracing-subscribersrc/server/Cargo.toml
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 1

Installing crates:common@0.1.0 pulls in 10 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
bincode1.3.3directunknown1

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 statisticscrates.io.