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

ClickHouse / clickhouse-rs

Official pure Rust typed client for ClickHouse DB

RustApache-2.0★ 553 stars⑂ 171 forkssince Oct 2020View on GitHub ↗

ClickHouse/clickhouse-rs holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Vitality (85/100) and lowest on Security (63/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

ClickHouseOrganization · verified domain
2,008 followers371 public repossince Sep 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioclickhouse0.15.21,178,951464 days agodatabasedriverhypertokioclickhouse
crates.ioclickhouse-types0.1.3585,34054 days ago
crates.ioclickhouse-macros0.3.0568,2831328 days ago
crates.ioclickhouse-ext-arrow0.1.016,389189 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
24.2/36Commit cadence35/52 weeks with commits
18/18Commit volume100 commits in the last year
10/10OpenSSF Scorecard: Maintained21 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year100
human_commit_share1
days_since_last_push4
active_weeks_last_year35
How it's scored
16.2/27Ships releases46 version tags (no GitHub releases)
36/36Release recencylatest release 4 days ago
19.8/27Release cadencea release every ~75.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count46
latest_release_tagv0.15.2
releases_from_tagsyes
days_since_latest_release4
mean_days_between_releases75.1
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?

85Excellent · 17% of overall
How it's scored
44.5/60Stars553 stars
18.6/25Forks171 forks
5.6/15Watchers11 watchers
Inputs used
forks171
stars553
watchers11
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Monthly downloads2,348,963 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesclickhouse, clickhouse-types, clickhouse-macros, clickhouse-ext-arrow
dependents
ecosystemscrates
total_downloads20,328,949
monthly_downloads2,348,963
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

75Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.7/22.5Commit distributiontop contributor authored 66% of commits
13.5/13.5Contributor breadth52 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled52
top_contributor_share0.657
How it's scored
30.9/42Issue resolution74% of issues closed
21.3/30PR acceptance155/218 decided PRs merged
8/13Newcomer PR acceptance8/13 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 25/30 approved changesets -- score normalized to 8
Inputs used
merged_prs155
open_issues63
closed_issues175
prs_merged_7d2
prs_decided_7d3
prs_merged_30d10
prs_decided_30d19
issue_closed_ratio0.735
closed_unmerged_prs63
first_time_authors_30d7
first_time_prs_merged_30d8
first_time_prs_decided_30d13
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
23.7/25Owner reach2,008 followers of ClickHouse
25/25Track record371 public repos, account ~7 yr old
Inputs used
followers2,008
owner_typeOrganization
is_verifiedyes
owner_loginClickHouse
public_repos371
account_age_days2,556

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable4 package(s) on crates
35/35Publish recencylatest publish 4 days ago
20/20Version history46 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesclickhouse, clickhouse-types, clickhouse-macros, clickhouse-ext-arrow
ecosystemscrates
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configCargo.toml ([lints]), clippy.toml, rustfmt.toml, types/Cargo.toml ([lints])
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests26 out of 27 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://clickhouse.com
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsclickhouse, http, rust, streaming, tokio
has_wikino
homepagehttps://clickhouse.com
docs_sitehttps://clickhouse.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.2/2.5CI-Tests26 out of 27 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 25/30 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 11 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
7.5/7.5Maintained21 commit(s) and 1 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
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): 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
advisories0
affected_packages0
assessed_packages1
unassessed_packages55
affected_by_severitynone
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 1 resolved dependencies against OSV. 55 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.

74Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://clickhouse.com/llms.txt)
40/40Legible commit history97 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://clickhouse.com/llms.txt
legible_history_share0.97
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, ext-arrow/Cargo.toml, macros/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configCargo.toml ([lints]), clippy.toml, rustfmt.toml, types/Cargo.toml ([lints])
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentDockerfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifestsCargo.toml, ext-arrow/Cargo.toml, macros/Cargo.toml, types/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
54.6/55Manageable file sizes1/132 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes83,136
source_files_sampled132
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

553GitHub stars
52contributors
100commits, last 12 months
4days since last push
46releases
1bus factor
63open issues
crates.iopackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 171 ⇿
0Stars
171Forks
39Releases

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.

0408012016020016642020-122023-102026-08
Major 0Minor 10Patch 29

Each point covers 6 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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 09:05 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests26 out of 27 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 25/30 approved changesets -- score normalized to 8
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained21 commit(s) and 1 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
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 44
RegistryPackageVersion constraintManifest
crates.ioclickhouse-macros0.3.0Cargo.toml
crates.ioclickhouse-types0.1.3Cargo.toml
crates.ioserde1.0.106Cargo.toml
crates.ioserde_json1Cargo.toml
crates.iohalf2.7.1Cargo.toml
crates.iothiserror2.0Cargo.toml
crates.iobytes1.5.0Cargo.toml
crates.iotokio1.0.1Cargo.toml
crates.iohttp-body-util0.1.2Cargo.toml
crates.iohyper1.4Cargo.toml
crates.iohyper-util0.1.6Cargo.toml
crates.iohyper-tls0.6.0Cargo.toml
crates.iorustls0.23Cargo.toml
crates.iohyper-rustls0.27.3Cargo.toml
crates.iourl2.1.1Cargo.toml
crates.iofutures-util0.3.5Cargo.toml
crates.iofutures-channel0.3.30Cargo.toml
crates.iolz4_flex0.11.6Cargo.toml
crates.iocityhash-rs=1.0.1Cargo.toml
crates.iozstd0.13Cargo.toml
crates.iouuid1Cargo.toml
crates.iotime0.3Cargo.toml
crates.iochrono0.4Cargo.toml
crates.iobstr1.11.0Cargo.toml
crates.ioquanta0.12Cargo.toml
crates.iohashbrown0.17.1Cargo.toml
crates.iobnum0.13.0Cargo.toml
crates.iotracing0.1.44Cargo.toml
crates.ioopentelemetry0.31.0Cargo.toml
crates.ioopentelemetry-http0.31.0Cargo.toml
crates.ioarrow-array58ext-arrow/Cargo.toml
crates.ioarrow-buffer58ext-arrow/Cargo.toml
crates.ioarrow-ipc58ext-arrow/Cargo.toml
crates.ioarrow-schema58ext-arrow/Cargo.toml
crates.ioarrow-select58ext-arrow/Cargo.toml
crates.iotokio1ext-arrow/Cargo.toml
crates.iotracing0.1ext-arrow/Cargo.toml
crates.ioclickhouse0.15.1ext-arrow/Cargo.toml
crates.ioproc-macro21.0macros/Cargo.toml
crates.iosyn2.0macros/Cargo.toml
crates.ioquote1.0macros/Cargo.toml
crates.ioserde_derive_internals0.29.1macros/Cargo.toml
crates.iothiserror2.0types/Cargo.toml
crates.iobytes1.10.1types/Cargo.toml
All dependencies 56

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

RegistryPackageVersionRelation
crates.ioarrow-arraydirect
crates.ioarrow-bufferdirect
crates.ioarrow-ipcdirect
crates.ioarrow-schemadirect
crates.ioarrow-selectdirect
crates.iobnumdirect
crates.iobstrdirect
crates.iobytesdirect
crates.iochronodirect
crates.iocityhash-rs1.0.1direct
crates.ioclickhousedirect
crates.ioclickhouse-macrosdirect
crates.ioclickhouse-typesdirect
crates.iofutures-channeldirect
crates.iofutures-utildirect
crates.iohalfdirect
crates.iohashbrowndirect
crates.iohttp-body-utildirect
crates.iohyperdirect
crates.iohyper-rustlsdirect
crates.iohyper-tlsdirect
crates.iohyper-utildirect
crates.iolz4_flexdirect
crates.ioopentelemetrydirect
crates.ioopentelemetry-httpdirect
crates.ioproc-macro2direct
crates.ioquantadirect
crates.ioquotedirect
crates.iorustlsdirect
crates.ioserdedirect
crates.ioserde_derive_internalsdirect
crates.ioserde_jsondirect
crates.iosyndirect
crates.iothiserrordirect
crates.iotimedirect
crates.iotokiodirect
crates.iotracingdirect
crates.iourldirect
crates.iouuiddirect
crates.iozstddirect
crates.ioarrowindirect
crates.iocriterionindirect
crates.iofixnumindirect
crates.ioindexmapindirect
crates.ioinstaindirect
crates.ioopentelemetry-otlpindirect
crates.ioopentelemetry-stdoutindirect
crates.ioopentelemetry_sdkindirect
crates.ioprettypleaseindirect
crates.iorandindirect
crates.iorustc-hashindirect
crates.ioserde_bytesindirect
crates.ioserde_reprindirect
crates.iotracing-opentelemetryindirect
crates.iotracing-subscriberindirect
crates.iotrybuildindirect
Dependency advisories 0

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

No known advisories affect the assessed dependencies.

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.