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

@uvrn/store-sqlite

v4.0.0

Published

Zero-signup durable persistence for UVRN: every store interface implemented against a single local SQLite file, plus pushToNetwork() sync to the UVRN registry

Readme

@uvrn/store-sqlite

Every UVRN store interface implemented against one local SQLite file — durable and zero-signup. This is the file-based zero-external path: state survives restarts without any service account, and the same file + interfaces are the local store of the UVRN desktop dashboard.

What it implements

| Class | Interface (owner) | Persists | |---|---|---| | SqliteCanonStore | CanonStore (@uvrn/canon) | canonized receipts (immutable, INSERT OR IGNORE) | | SqliteIdentityStore | IdentityStore (@uvrn/identity) | reputation scores + activity history | | SqliteTimelineStore | TimelineStore (@uvrn/timeline) + write side | drift snapshots + canon events | | SqliteWatchStore | WatchStore (@uvrn/watch, v4) | watcher subscriptions | | SqliteAgentStateStore | AgentStateStore (@uvrn/agent, v4) | agent claims, last snapshots, failure counts | | SqliteReceiptStore | — (this package) | local NetworkReceipt outbox + pushToNetwork() |

Storage stays an injected interface — protocol packages ship no storage of their own (house rule); this package is one reference implementation. In-memory mocks remain the zero-dependency default everywhere.

Driver

better-sqlite3 is an optional peer dependency, required lazily — importing this package's types never demands the native module. Bring your own driver via openUvrnDatabase(path, driver) if you prefer (anything with exec/prepare/close).

Quickstart

import { openUvrnDatabase, SqliteIdentityStore, SqliteAgentStateStore,
         SqliteWatchStore, SqliteReceiptStore } from '@uvrn/store-sqlite';
import { IdentityRegistry } from '@uvrn/identity';

const db = openUvrnDatabase('./uvrn.db');           // ':memory:' for throwaway

const registry = new IdentityRegistry({ store: new SqliteIdentityStore(db) });
// ... agent: new Agent({ ..., stateStore: new SqliteAgentStateStore(db) })
// ... watcher: new Watcher({ ..., store: new SqliteWatchStore(db) })

pushToNetwork — the satellite sync (SPEC/uvrn-network-v1.md §6)

const outbox = new SqliteReceiptStore(db);
outbox.save(signedNetworkReceipt);                  // idempotent on receiptHash

const report = await outbox.pushToNetwork(workerClient);
// { pushed, failed: [{receiptHash, status, error}], remaining }

Unsynced receipts submit oldest-first. A 2xx marks the row synced; a 5xx or transport failure stops the run (server trouble — retry later, order preserved); a 4xx is surfaced in the report and the receipt stays in the outbox for you to inspect — never mutated-and-retried.

WorkerClient is the minimal contract { submitReceipt(receipt) → { ok, status, registryId? } }; any client of the registry's POST /receipts satisfies it.

Schema

Additive-only; every table stores the full object as JSON plus indexed query columns. The file is yours — back it up by copying it.