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

@oribos/rag

v0.9.0

Published

Oribos RAG capability package — semantic recall over message history: wrap a MemoryStore to index saved messages with your embedding model and pull older relevant messages back into the recall window, no dependencies beyond the @oribos/core peer.

Readme

@oribos/rag

Semantic recall over message history — the RAG capability package. It wraps a MemoryStore so that every message Memory.save persists is indexed with your embedding model, and the window Memory.recall returns is merged with older, semantically related messages. One seam, no core changes:

import { Memory } from '@oribos/core/memory';
import { createSemanticMemoryStore } from '@oribos/rag';
import { openai } from '@ai-sdk/openai';

const memory = new Memory({
  storage: createSemanticMemoryStore({
    embedder: openai.textEmbeddingModel('text-embedding-3-small'),
  }),
  lastMessages: 10,
});

How it works

  • Save indexes. createSemanticMemoryStore wraps any MemoryStore (absent = the core's in-memory default). Each persisted message's text (system / user / assistant text parts) goes to the embedder and into a vector index — inline, within the save call. Messages persist first; an embedder failure rejects the save explicitly.
  • Recall merges. A cursorless window read embeds the window's last user message and merges positively-similar older messages back into the result, in chronological position — the recall window forgets less. Paging with before passes through untouched; an empty or textless window spends no embedding. topK defaults to 3.
  • Pins kept. Messages are immutable (the index is a derived cache of full stored messages), recall stays the single query entry, deleteThread cascades to the index, and the working-memory capability of the wrapped store passes through.

The embedder follows the framework's model contract pattern: a vendored structural subset of the AI SDK provider specification's embedding model interface (v4). Any embedding model instance from a provider package satisfies it — no adapter, no registry. The vector index is the package's own port: createInMemoryVectorIndex() ships as the zero-dependency default; an external vector database rides as your VectorIndex implementation, so its dependency travels with this package (or your adapter), never the core. Unconfigured, nothing exists — opt-in, zero cost, no resident pipeline.

See docs/architecture/memory.md (「语义召回」) and examples/semantic-recall.