npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

ck-orm

v0.0.34

Published

ClickHouse ORM for modern JS runtimes

Readme

⚠️ Before version 0.1.0, there will be significant API adjustments. If needed, please pin the version number.

CK-ORM

It gives you:

  • a schema DSL for ClickHouse tables and columns
  • a typed query builder for the common path
  • raw SQL when ClickHouse-specific syntax is the better tool
  • session helpers for temporary-table workflows
  • observability through a logger and query lifecycle plugins, with OpenTelemetry tracing in ck-orm/otel

Installation

bun add ck-orm
npm install ck-orm
pnpm add ck-orm
yarn add ck-orm

ck-orm has no required dependencies. OpenTelemetry tracing is a separate entry point, ck-orm/otel, and @opentelemetry/api is an optional peer dependency used only by it. The main ck-orm entry never imports OpenTelemetry, so an application, browser bundle or edge worker that does not trace installs and bundles none of it. To trace queries, install the API and an SDK, then follow the OpenTelemetry plugin setup in the reference.

Example

import { ck, ckTable, ckType, clickhouseClient, fn } from "ck-orm";

const probes = ckTable("probes", {
  probeId: ckType.string("probe_id"),
  signal: ckType.decimal({ precision: 20, scale: 5 }),
  status: ckType.int16(),
});

const db = clickhouseClient({ host: "http://127.0.0.1:8123" });

const rows = await db
  .select({ probeId: probes.probeId, total: fn.sum(probes.signal).as("total") })
  .from(probes)
  .where(ck.eq(probes.status, 1))
  .groupBy(probes.probeId);
// rows: { probeId: string; total: string }[]

Documentation

  • ck-orm.lyz.cloud: the full reference, covering the schema DSL, query builder, writes, raw SQL, sessions, observability, errors and security.
  • llms.txt: the same reference for AI coding agents, with one markdown file per section.
  • examples/: runnable examples, each a main.ts with a main.test.ts and a package.json; the site shows the SQL each one sends.
  • e2e/: runnable scenarios against a real ClickHouse server.

The documentation source lives in docs/.

License

MIT