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

@opencodehub/storage

v0.1.0

Published

OpenCodeHub — DuckDB graph store (@duckdb/node-api + hnsw_acorn + fts)

Readme

@opencodehub/storage

Graph store abstraction for OpenCodeHub. Backed by DuckDB with HNSW ANN search (hnsw_acorn) and full-text search (fts), with an optional @ladybugdb/core graph-database layer.

Surface

import { openStore, StorageAdapter } from "@opencodehub/storage";

const store = await openStore({ repoRoot: "/path/to/repo" });
// store: StorageAdapter — read/write graph nodes and edges
  • openStore — probes for @ladybugdb/core and uses the graph-database backend when available; falls back to the DuckDB-only layout with a one-shot advisory on TTY or OCH_VERBOSE=1.
  • StorageAdapter — uniform interface used by ingestion, analysis, search, and MCP. Abstracts over the two backends.
  • test-utils — exported as @opencodehub/storage/test-utils for in-memory stores in tests (packages/storage/src/test-utils/index.ts).

Backend selection

| CODEHUB_STORE | Backend | |---|---| | unset (default) | graph-database if @ladybugdb/core available, else DuckDB | | duck | DuckDB only (single graph.duckdb file) | | lbug | @ladybugdb/core required; error if not installed |

When both graph.duckdb and graph.lbug exist in the same <repo>/.codehub/, the newer-mtime file wins. See ADR 0013 for rationale.

Design

  • All writes go through write-file-atomic indirectly — the DuckDB checkpoint is atomic at the WAL level.
  • Connection pooling is handled by the caller (the MCP server's connection-pool.ts); the store itself is single-writer, multi-reader.
  • The hnsw_acorn extension is loaded lazily — it is a no-op if embeddings were not generated during ingestion.