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

@oberik/sdk

v0.79.0

Published

TypeScript client for Oberik — chat with citations, tools, sandboxed compute and scheduling over your own data.

Readme

@oberik/sdk

TypeScript client for Oberik — give your product AI over your customers' own data: retrieval with citations, your own tools, sandboxed compute, files and media, scheduling.

npm install @oberik/sdk

Quick start

Your backend mints a short-lived token for one end-user; the SDK asks for a new one when it expires, so an expiry never surfaces at a call site.

import { createClient } from "@oberik/sdk";

const ai = createClient({
  // baseUrl defaults to the hosted API; set it for a self-hosted deployment.
  getToken: async ({ expired }) => fetchTokenFromYourBackend({ force: expired }),
});

const res = await ai.chat.send({ message: "How did Q3 revenue trend?", tags: ["finance"] });

res.content;    // grounded answer
res.citations;  // document · page · quote

Streaming, which is what you want in a UI:

const handle = ai.chat.stream(
  { message: input },
  {
    onToken: (_delta, full) => render(full),
    onReasoning: (_delta, full) => showThinking(full),   // reasoning models
    onToolStart: (name) => setStatus(`Running ${name}…`),
    onCitations: (cs) => showSources(cs),
    onAttachments: (files) => offerDownloads(files),
  },
);
const done = await handle.done;

A dropped connection resumes the same run rather than restarting it, so a closed laptop lid mid-answer doesn't lose the answer or pay for it twice.

What's in the box

  • Chat — blocking or streaming, with citations, unified source pills, guardrail flags and finish_reason.
  • Your own tools — register a handler and chat.run/chat.stream dispatch it and resume for you; or drive the pause/resume loop yourself.
  • Documents — resumable presigned multipart upload straight to storage, ranged resumable download, retrieval, chunk inspection, ACLs.
  • Sandboxed compute — start, pause, resume and reattach a workspace; push and pull files.
  • Scheduling, connected sources, audit — the rest of the API, typed.

Zero dependencies, works in Node 18+ and in the browser, ESM and CommonJS.

Docs

Full documentation, including how to mint tokens and which capabilities gate what: https://oberik.com/docs

Development

The client is a single file kept at client/agent-framework.ts in the Oberik repository; src/index.ts here is a symlink to it, so the published package, the dashboard's own playground and the docs all use one source. Building emits ESM, CommonJS and types:

npm run build     # dist/esm, dist/cjs, .d.ts
npm run check     # asserts the tarball is actually usable before publishing

npm publish runs both automatically via prepublishOnly.