Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 11:03 UTC

cybersemics / treecrdt

TreeCRDT Sqlite Extension

TypeScript · RustMIT★ 2 stars⑂ 1 forksince Dec 2025View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

cybersemics/treecrdt holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (34/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

16 followers15 public repossince Jul 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@treecrdt/discovery0.1.02,0111122 days ago
npm@treecrdt/interface0.2.02,2022118 days ago
npm@treecrdt/auth0.1.22,018366 days ago
npm@treecrdt/sync0.1.22,293366 days ago

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
27/36Commit cadence39/52 weeks with commits
18/18Commit volume833 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year833
human_commit_share0.94
days_since_last_push0
active_weeks_last_year39

Release discipline

100Exceptional
How it's scored
27/27Ships releases38 releases published
36/36Release recencylatest release 35 days ago
27/27Release cadencea release every ~3.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count38
latest_release_tag@treecrdt/wa-sqlite@0.4.2
releases_from_tagsno
days_since_latest_release35
mean_days_between_releases3.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?

34At Risk · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks1 forks
0/15Watchers1 watchers
Inputs used
forks1
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
52.4/80Monthly downloads8,524 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@treecrdt/discovery, @treecrdt/interface, @treecrdt/auth, @treecrdt/sync
dependents
ecosystemsnpm
total_downloads
monthly_downloads8,524
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.2/22.5Commit distributiontop contributor authored 68% of commits
4.1/13.5Contributor breadth3 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.682
How it's scored
25.5/42Issue resolution61% of issues closed
24.9/30PR acceptance118/142 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_prs118
open_issues26
closed_issues40
prs_merged_7d1
prs_decided_7d1
prs_merged_30d7
prs_decided_30d8
issue_closed_ratio0.606
closed_unmerged_prs24
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
0/20Verified domain
8.8/25Owner reach16 followers of cybersemics
20.8/25Track record15 public repos, account ~7 yr old
Inputs used
followers16
owner_typeOrganization
is_verifiedno
owner_logincybersemics
public_repos15
account_age_days2,609
How it's scored
25/25Published & resolvable4 package(s) on npm
35/35Publish recencylatest publish 66 days ago
12/20Version history3 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@treecrdt/discovery, @treecrdt/interface, @treecrdt/auth, @treecrdt/sync
ecosystemsnpm
any_deprecatedno
min_days_since_publish66

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
16/16Linter config.clippy.toml, rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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.5Maintained30 commit(s) and 15 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
0/7.5Vulnerabilities35 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): 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.

82Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history76 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.809
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes1,980
How it's scored
12.6/18One-command bootstrapCargo.toml, packages/treecrdt-core/Cargo.toml, packages/treecrdt-postgres-napi/native-rs/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.clippy.toml, rustfmt.toml
11/11Static type checkingexamples/playground/tsconfig.json, packages/discovery-server-node/tsconfig.json, packages/discovery/tsconfig.json, packages/sync-protocol/material/postgres/tsconfig.json, packages/sync-protocol/material/sqlite/tsconfig.json, packages/sync-protocol/protocol/tsconfig.json, packages/sync-protocol/server/core/tests/tsconfig.json, packages/sync-protocol/server/core/tsconfig.json, packages/sync-protocol/server/postgres-node/tsconfig.json, packages/treecrdt-auth/tsconfig.json, packages/treecrdt-benchmark/tsconfig.json, packages/treecrdt-crypto/tsconfig.json, packages/treecrdt-engine-conformance/tsconfig.json, packages/treecrdt-postgres-napi/tsconfig.json, packages/treecrdt-riblt-wasm-js/tsconfig.json, packages/treecrdt-sqlite-node/tsconfig.json, packages/treecrdt-sync/tsconfig.json, packages/treecrdt-ts/tsconfig.json, packages/treecrdt-wa-sqlite/e2e/tsconfig.json, packages/treecrdt-wa-sqlite/tsconfig.json, packages/treecrdt-wasm-js/tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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
lockfilesCargo.lock, pnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/playground/tsconfig.json, packages/discovery-server-node/tsconfig.json, packages/discovery/tsconfig.json, packages/sync-protocol/material/postgres/tsconfig.json, packages/sync-protocol/material/sqlite/tsconfig.json, packages/sync-protocol/protocol/tsconfig.json, packages/sync-protocol/server/core/tests/tsconfig.json, packages/sync-protocol/server/core/tsconfig.json, packages/sync-protocol/server/postgres-node/tsconfig.json, packages/treecrdt-auth/tsconfig.json, packages/treecrdt-benchmark/tsconfig.json, packages/treecrdt-crypto/tsconfig.json, packages/treecrdt-engine-conformance/tsconfig.json, packages/treecrdt-postgres-napi/tsconfig.json, packages/treecrdt-riblt-wasm-js/tsconfig.json, packages/treecrdt-sqlite-node/tsconfig.json, packages/treecrdt-sync/tsconfig.json, packages/treecrdt-ts/tsconfig.json, packages/treecrdt-wa-sqlite/e2e/tsconfig.json, packages/treecrdt-wa-sqlite/tsconfig.json, packages/treecrdt-wasm-js/tsconfig.json
agent_commit_share0
toolchain_manifestsCargo.toml, packages/treecrdt-core/Cargo.toml, packages/treecrdt-postgres-napi/native-rs/Cargo.toml, packages/treecrdt-postgres-rs/Cargo.toml, packages/treecrdt-riblt-wasm/Cargo.toml, packages/treecrdt-sqlite-ext/Cargo.toml, packages/treecrdt-test-support/Cargo.toml, packages/treecrdt-wasm/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54/55Manageable file sizes6/317 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes87,875
source_files_sampled317
oversized_source_files6
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)docs/sync/v0.proto, docs/sync/v0/filters.proto, docs/sync/v0/messages.proto, docs/sync/v0/ops.proto, docs/sync/v0/types.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesdocs/sync/v0.proto, docs/sync/v0/filters.proto, docs/sync/v0/messages.proto, docs/sync/v0/ops.proto, docs/sync/v0/types.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

2GitHub stars
3contributors
833commits, last 12 months
0days since last push
38releases
1bus factor
26open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'treecrdt-core' from its registry
  • Could not fetch crates package 'treecrdt-wasm' from its registry
  • Could not fetch npm package '@treecrdt/wasm' from its registry
  • Could not fetch crates package 'treecrdt-riblt-wasm' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-18 11:02 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 15 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
0Vulnerabilities35 existing vulnerabilities detected
Direct dependencies 51
RegistryPackageVersion constraintManifest
npm@treecrdt/discoveryworkspace:*packages/discovery-server-node/package.json
npm@noble/ed25519^3.0.0packages/treecrdt-auth/package.json
npm@noble/hashes^1.8.0packages/treecrdt-auth/package.json
npm@treecrdt/interfaceworkspace:*packages/treecrdt-auth/package.json
npm@treecrdt/sync-protocolworkspace:*packages/treecrdt-auth/package.json
npmcborg^4.3.2packages/treecrdt-auth/package.json
npm@treecrdt/interfaceworkspace:*packages/treecrdt-benchmark/package.json
npmcommander^14.0.2packages/treecrdt-benchmark/package.json
crates.ioserde1.0packages/treecrdt-core/Cargo.toml
crates.ioserde_bytes0.11packages/treecrdt-core/Cargo.toml
crates.ioserde_json1.0packages/treecrdt-core/Cargo.toml
crates.iothiserror1.0packages/treecrdt-core/Cargo.toml
crates.iochrono0.4packages/treecrdt-core/Cargo.toml
npm@noble/ed25519^3.0.0packages/treecrdt-crypto/package.json
npm@noble/hashes^1.8.0packages/treecrdt-crypto/package.json
npmcborg^4.3.2packages/treecrdt-crypto/package.json
npm@treecrdt/authworkspace:*packages/treecrdt-engine-conformance/package.json
npm@treecrdt/interfaceworkspace:*packages/treecrdt-engine-conformance/package.json
npm@treecrdt/sync-protocolworkspace:*packages/treecrdt-engine-conformance/package.json
npm@treecrdt/sync-sqliteworkspace:*packages/treecrdt-engine-conformance/package.json
npm@treecrdt/wasmworkspace:*packages/treecrdt-engine-conformance/package.json
npm@treecrdt/interfaceworkspace:*packages/treecrdt-postgres-napi/package.json
npm@treecrdt/sync-protocolworkspace:*packages/treecrdt-postgres-napi/package.json
crates.ioblake31.6packages/treecrdt-postgres-rs/Cargo.toml
crates.iopostgres0.19packages/treecrdt-postgres-rs/Cargo.toml
crates.ioserde_json1.0packages/treecrdt-postgres-rs/Cargo.toml
crates.iotreecrdt-corepackages/treecrdt-postgres-rs/Cargo.toml
crates.ioribltpackages/treecrdt-riblt-wasm/Cargo.toml
crates.ioserde1packages/treecrdt-riblt-wasm/Cargo.toml
crates.ioserde-wasm-bindgen0.6packages/treecrdt-riblt-wasm/Cargo.toml
crates.iowasm-bindgen0.2packages/treecrdt-riblt-wasm/Cargo.toml
crates.ioblake31.6packages/treecrdt-sqlite-ext/Cargo.toml
crates.iotreecrdt-corepackages/treecrdt-sqlite-ext/Cargo.toml
crates.iosqlite3ext-sys0.0.1packages/treecrdt-sqlite-ext/Cargo.toml
crates.ioserde1.0packages/treecrdt-sqlite-ext/Cargo.toml
crates.ioserde_json1.0packages/treecrdt-sqlite-ext/Cargo.toml
npm@treecrdt/interfaceworkspace:*packages/treecrdt-sqlite-node/package.json
npm@treecrdt/sync-sqliteworkspace:*packages/treecrdt-sqlite-node/package.json
npm@treecrdt/discoveryworkspace:*packages/treecrdt-sync/package.json
npm@treecrdt/interfaceworkspace:*packages/treecrdt-sync/package.json
npm@treecrdt/sync-protocolworkspace:*packages/treecrdt-sync/package.json
npm@treecrdt/sync-sqliteworkspace:*packages/treecrdt-sync/package.json
crates.iotreecrdt-corepackages/treecrdt-test-support/Cargo.toml
npm@treecrdt/interfaceworkspace:*packages/treecrdt-wa-sqlite/package.json
npmcomlink^4.4.2packages/treecrdt-wa-sqlite/package.json
npm@treecrdt/interfaceworkspace:*packages/treecrdt-wasm-js/package.json
crates.iotreecrdt-corepackages/treecrdt-wasm/Cargo.toml
crates.iowasm-bindgen0.2packages/treecrdt-wasm/Cargo.toml
crates.ioserde1packages/treecrdt-wasm/Cargo.toml
crates.ioserde_json1packages/treecrdt-wasm/Cargo.toml
crates.ioserde-wasm-bindgen0.6packages/treecrdt-wasm/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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