Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-23 00:33 UTC

obsessiondb / chkit

ClickHouse schema and migration CLI for TypeScript projects

TypeScriptMIT★ 21 stars⑂ 2 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

obsessiondb/chkit holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (86/100) and lowest on Security (46/100). It was last updated 2 days ago. A single contributor accounts 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

Obsession DBOrganization
11 followers5 public repossince Jan 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmchkit0.1.2-beta.52,708325 days agoclickhouseschemamigrationstypescriptdatabasecli
npm@chkit/core0.1.2-beta.53,803375 days agoclickhouseschemamigrationstypescriptdatabase
npm@chkit/codegen0.1.2-beta.53,169365 days agoclickhousecodegenmigrations
npm@chkit/clickhouse0.1.2-beta.53,991375 days agoclickhousedatabaseclient
npm@chkit/plugin-pull0.1.2-beta.53,358365 days agoclickhouseintrospectionschemachkit-plugin
npmcreate-chkit0.1.2-beta.51,279115 days agoclickhouseschemamigrationstypescriptscaffoldcreatechkit
npm@chkit/plugin-codegen0.1.2-beta.53,143335 days agoclickhousetypescriptcodegenzodchkit-plugin
npm@chkit/plugin-backfill0.1.2-beta.52,715365 days agoclickhousebackfilldata-migrationchkit-plugin

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
14.5/36Commit cadence21/52 weeks with commits
18/18Commit volume297 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year297
human_commit_share1
days_since_last_push2
active_weeks_last_year21
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno 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?

56Moderate · 17% of overall
How it's scored
21.1/60Stars21 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars21
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/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_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
58.4/80Monthly downloads24,166 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageschkit, @chkit/core, @chkit/codegen, @chkit/clickhouse, @chkit/plugin-pull, create-chkit, @chkit/plugin-codegen, @chkit/plugin-backfill
dependents
ecosystemsnpm
total_downloads
monthly_downloads24,166
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.5/22.5Commit distributiontop contributor authored 89% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.889
How it's scored
24.5/42Issue resolution58% of issues closed
28.2/30PR acceptance174/185 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs174
open_issues5
closed_issues7
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.583
closed_unmerged_prs11
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
7.8/25Owner reach11 followers of obsessiondb
6.7/25Track record5 public repos, account ~0 yr old
Inputs used
followers11
owner_typeOrganization
is_verified
owner_loginobsessiondb
public_repos5
account_age_days181
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable8 package(s) on npm
35/35Publish recencylatest publish 5 days ago
20/20Version history37 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageschkit, @chkit/core, @chkit/codegen, @chkit/clickhouse, @chkit/plugin-pull, create-chkit, @chkit/plugin-codegen, @chkit/plugin-backfill
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests20 out of 20 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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://chkit.obsessiondb.com
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicscli, clickhouse, clickhouse-migrations, database, migrations, schema, typescript
has_wikino
homepagehttps://chkit.obsessiondb.com
docs_sitehttps://chkit.obsessiondb.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

46Weak · 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-Tests20 out of 20 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
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 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.5Maintained30 commit(s) and 11 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
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities51 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history92 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.92
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,596
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingapps/docs/tsconfig.json, packages/cli/tsconfig.json, packages/clickhouse/tsconfig.json, packages/codegen/tsconfig.json, packages/core/tsconfig.json, packages/create-chkit/tsconfig.json, packages/plugin-backfill/tsconfig.json, packages/plugin-codegen/tsconfig.json, packages/plugin-obsessiondb/tsconfig.json, packages/plugin-pull/tsconfig.json, tsconfig.json
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice17 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_configsapps/docs/tsconfig.json, packages/cli/tsconfig.json, packages/clickhouse/tsconfig.json, packages/codegen/tsconfig.json, packages/core/tsconfig.json, packages/create-chkit/tsconfig.json, packages/plugin-backfill/tsconfig.json, packages/plugin-codegen/tsconfig.json, packages/plugin-obsessiondb/tsconfig.json, packages/plugin-pull/tsconfig.json, tsconfig.json
agent_commit_share0.17
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/276 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes56,670
source_files_sampled276
oversized_source_files0
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

21GitHub stars
3contributors
297commits, last 12 months
2days since last push
0releases
1bus factor
5open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index npm:chkit@0.1.2-beta.5; advisories assessed against the repository dependency graph instead

More detail

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

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.

111222212026-072026-072026-07
OpenSSF Scorecard 4.6 / 10
4.6aggregate

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-23 00:32 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests20 out of 20 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 11 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
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities51 existing vulnerabilities detected
Direct dependencies 33
RegistryPackageVersion constraintManifest
npmfast-glob^3.3.2packages/cli/package.json
npm@chkit/clickhouseworkspace:*packages/cli/package.json
npm@chkit/codegenworkspace:*packages/cli/package.json
npm@chkit/coreworkspace:*packages/cli/package.json
npm@logtape/logtape^2.0.5packages/cli/package.json
npm@chkit/coreworkspace:*packages/clickhouse/package.json
npm@clickhouse/client^1.18.0packages/clickhouse/package.json
npm@logtape/logtape^2.0.5packages/clickhouse/package.json
npmp-retry^7.1.1packages/clickhouse/package.json
npm@chkit/coreworkspace:*packages/codegen/package.json
npmfast-glob^3.3.2packages/core/package.json
npmjiti^2.7.0packages/core/package.json
npm@chkit/plugin-obsessiondbworkspace:*packages/create-chkit/package.json
npm@clack/prompts^1.4.0packages/create-chkit/package.json
npmcommander^14.0.3packages/create-chkit/package.json
npmgiget^3.2.0packages/create-chkit/package.json
npmpicocolors^1.1.1packages/create-chkit/package.json
npm@chkit/clickhouseworkspace:*packages/plugin-backfill/package.json
npm@chkit/coreworkspace:*packages/plugin-backfill/package.json
npm@logtape/logtape^2.0.5packages/plugin-backfill/package.json
npmp-map^7.0.4packages/plugin-backfill/package.json
npmzod^4.3.6packages/plugin-backfill/package.json
npm@chkit/coreworkspace:*packages/plugin-codegen/package.json
npm@chkit/clickhouseworkspace:*packages/plugin-obsessiondb/package.json
npm@chkit/coreworkspace:*packages/plugin-obsessiondb/package.json
npm@chkit/plugin-backfillworkspace:*packages/plugin-obsessiondb/package.json
npm@clack/prompts^1.4.0packages/plugin-obsessiondb/package.json
npm@orpc/client1.13.4packages/plugin-obsessiondb/package.json
npm@orpc/contract1.13.4packages/plugin-obsessiondb/package.json
npmzod^4.3.6packages/plugin-obsessiondb/package.json
npm@chkit/clickhouseworkspace:*packages/plugin-pull/package.json
npm@chkit/coreworkspace:*packages/plugin-pull/package.json
npmzod^4.3.6packages/plugin-pull/package.json
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.27.0 — full methodology · metrics wiki.

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