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

@oxilite/node

v0.3.0

Published

oxilite for Node.js: an Oxigraph-compatible SPARQL 1.1 and openCypher store on SQLite

Readme

@oxilite/node

npm license

An Oxigraph-compatible SPARQL 1.1 store for Node.js, on SQLite. The API of Oxigraph's JavaScript package, with RDF/JS terms, on a single SQLite file. Also query the same data with openCypher, reason with RDFS / OWL, and search text with FTS5.

Website · npm · Guide and architecture · Changelog and issues

npm install @oxilite/node

Quick start

import { Store, namedNode, literal, quad, type Term } from "@oxilite/node";

const store = new Store("data.sqlite");               // new Store() for an in-memory store
store.load(`@prefix ex: <http://example.com/> .
  ex:ada a ex:Person ; ex:name "Ada" ; ex:knows ex:alan .`, { format: "text/turtle" });

store.add(quad(namedNode("http://example.com/alan"), namedNode("http://example.com/name"), literal("Alan")));

for (const row of store.query(
  "SELECT ?name WHERE { ?p <http://example.com/name> ?name }",
) as Map<string, Term>[]) {
  console.log(row.get("name")?.value);
}

store.update("DELETE WHERE { ?s <http://example.com/knows> ?o }");
console.log(store.size);

query returns what Oxigraph returns: an array of Maps for SELECT, a boolean for ASK, quads for CONSTRUCT / DESCRIBE, or a string when you pass results_format.

Cypher over the same data

const opts = { base: "http://example.com/" };
store.cypher("CREATE (:Person {name: 'Grace'})-[:KNOWS {since: 1950}]->(:Person {name: 'Ada'})", {}, opts);

const r = store.cypher(
  "MATCH (a:Person {name: $name})-[:KNOWS]->(b) RETURN b.name AS friend",
  { name: "Grace" }, opts,
);
console.log(r.records);                    // [{ friend: "Ada" }]
console.log(store.explainCypher("MATCH (n:Person) RETURN n", {}, opts));

Nodes are IRIs, labels are rdf:type, properties are literal triples, relationships are triples (with an RDF 1.2 reifier for their properties), so SPARQL sees everything Cypher writes. With reasoning: "rdfs", labels follow class hierarchies; SHACL shapes in the store check every write.

JSON-LD documents and Verifiable Credentials

// Any JSON-LD document: stored byte for byte, its RDF in a named graph (by default its @id).
const docs = store.jsonld();
docs.put(`{"@context": {"name": "http://schema.org/name"}, "@id": "urn:uuid:1234", "name": "Ada"}`);
store.query('ASK { GRAPH <urn:uuid:1234> { ?s <http://schema.org/name> "Ada" } }');   // true
docs.get("urn:uuid:1234")?.json;                         // the exact text you stored

// Verifiable Credentials (VCDM 1.1 and 2.0), W3C contexts bundled, proofs in their own graphs.
const vcs = store.credentials();
const id = vcs.put(credentialJson);                      // key = the credential's id
vcs.putPresentation(presentationJson);                   // also stores the embedded credentials
vcs.find({ issuer: "did:example:issuer", validAt: new Date() });   // indexed, no SPARQL

Options select how documents are keyed and where their triples go:

  • key: "id" (the default), { pointer: "/credentialSubject/id" }, "contentHash" or "explicit";
  • graph: "key" (the default), { template: "https://ex.org/g/{key}" }, { fixed: iri } or "default";
  • contexts (in memory), network: true (download unknown contexts), indexes.

Contexts can also be persisted with docs.putContext(iri, context). Errors are JsonLdError with a code, such as loading remote context failed, missing-key, invalid or graph-owned. docs.check() and docs.rebuild(key) repair document graphs edited with SPARQL UPDATE. Proofs are not verified.

API

| Method | Does | |---|---| | new Store(path? \| quads? \| options?) | Open a SQLite file, an in-memory store, or one filled with quads. Options: path, library (a libsqlite3 to load), graphIndex, textIndex | | query(sparql, options?) | SPARQL 1.1 query. Options as in Oxigraph, plus reasoning: "rdfs" \| "owl-ql" and include_inferred | | update(sparql) | SPARQL 1.1 Update, atomically | | load(data, options) / bulkLoad(data, options) | Parse Turtle, N-Triples, N-Quads, TriG, RDF/XML, JSON-LD… | | dump(options) | Serialize the store or one graph | | add, addAll, delete, has, match, size | Quad-level access with RDF/JS terms | | cypher(query, params?, options?) | openCypher read or write; returns { columns, rows, records, stats } | | jsonld(options?) | JSON-LD documents: put, putAll, get, remove, list, find, graphs, documentForGraph, putContext, removeContext, contexts, check, rebuild | | credentials(options?) | Verifiable Credentials: put, putPresentation, get, remove, find, and documents for the rest | | explain(sparql), explainUpdate, explainCypher | The SQL a statement compiles to, with the planner's notes | | materialize({ engine? }), clearInferences() | OWL 2 RL closure ("sql" or "reasonable") | | optimize(), backup(path), clear() | Refresh planner statistics, VACUUM INTO a copy, empty the store |

Oxigraph's own store.test.ts runs unchanged against this package.

Platforms

Version 0.2 ships a prebuilt native binary for macOS on Apple silicon (darwin-arm64). On other platforms, build it from a checkout of the repository with npm run build:native -w @oxilite/node (needs a Rust toolchain). For Cloudflare Workers, use @oxilite/d1, which needs no native code.

The oxilite family

oxilite is an Oxigraph-compatible RDF database and SPARQL 1.1 engine that stores its data in SQLite, so it runs anywhere SQLite runs: in-process, on a system or vendor libsqlite3, on Cloudflare D1 and in Durable Objects. The same data can be queried with SPARQL and openCypher, reasoned over with RDFS / OWL, and validated with SHACL and ShEx. Read the overview on oxilitedb.com and the full guide in the main README.

| Package | What it is for | |---|---| | oxilite | The store: a drop-in for oxigraph::store::Store, plus AsyncStore for D1 | | oxilite-core | The sans-IO core: term encoding, schema, SPARQL → SQL compiler and planner | | oxilite-rusqlite | In-process backend with a bundled SQLite (the default) | | oxilite-dylib | Backend that loads your own libsqlite3 at runtime | | oxilite-d1 | Cloudflare D1 backend for Rust Workers | | oxilite-cypher | openCypher over the same data, OWL- and SHACL-aware | | oxilite-jsonld | JSON-LD documents stored verbatim, one named graph each | | oxilite-vc | Verifiable Credentials: stored under their id, indexed, queryable | | oxilite-reason | OWL 2 RL materialization with reasonable | | oxilite-validate | SHACL and ShEx validation with rudof | | oxilite-cli | The oxilite command and a SPARQL endpoint like oxigraph serve | | @oxilite/node | Node.js bindings, API of Oxigraph's JS package | | @oxilite/d1 | Cloudflare D1 and Durable Objects from TypeScript (WebAssembly core) | | @oxilite/common | RDF/JS terms and shared TypeScript types |

License

Dual-licensed under MIT or Apache-2.0, at your option, like Oxigraph.