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

@usecarry/vercel-ai

v0.1.0

Published

Drop-in proof-carrying memory for the Vercel AI SDK — gate memory before generation and attach an Answer Receipt to every response.

Readme

@usecarry/vercel-ai

Drop-in proof-carrying memory for the Vercel AI SDK.

Wrap any model in one line. Carry gates the user's memory before generation — the model only ever sees authorized memory — and emits an Answer Receipt (what was used, what was blocked) on every call.

import { withCarryMemory, createMemoryStore } from "@usecarry/vercel-ai";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";

const store = createMemoryStore({
  memories: [
    { id: "m1", namespace: "health", content: "Allergic to penicillin" },
    { id: "m2", namespace: "billing", content: "Card ending 4242" },
  ],
  policy: { aria: { billing: false } }, // revoke billing for this agent
});

const model = withCarryMemory(openai("gpt-4o"), {
  store,
  agent: "aria",
  onReceipt: (r) => console.log(r.used, r.blockedNamespaces), // proof of what it used
});

const { text } = await generateText({ model, prompt: "Am I allergic to anything?" });
// → recalls only `health`, injects it, answers. `billing` is never fetched.

That's the whole integration. Works with generateText, streamText, generateObject — anything that takes a model.

Why

A raw vector-DB memory layer hands your model everything it retrieves and hopes for the best. Carry enforces an agent × namespace policy at retrieval, so a revoked namespace is never injected into the prompt — and every generation carries a receipt proving exactly what memory reached the model.

API

  • withCarryMemory(model, opts) — wraps a model with the Carry middleware. Returns the same model type.
  • carryMiddleware(opts) — the raw LanguageModelMiddleware if you compose your own wrapLanguageModel.
  • createMemoryStore({ memories, policy }) — an in-memory Carry vault (default-allow; policy[agent][ns] = false revokes).
  • CarryStore — implement recall(agent, query) to back it with your own store (Walrus, a DB, the carry CLI vault, …).

Options: { store, agent?, onReceipt? }. onReceipt(receipt) fires on every call with { agent, query, used, blockedNamespaces, createdAt }.

Part of Carry — proof-carrying memory for AI agents, stored on Walrus, enforced on Sui.

MIT © Carry