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

@usecarte/core

v0.1.0

Published

Framework-agnostic core for Carte: typed query carte, plan schema, validation, prompt generation.

Readme

@usecarte/core

Framework-agnostic kernel for Carte — a typed query carte for putting LLMs in front of databases without giving them SQL.

@usecarte/core defines the carte itself (a fixed list of named, typed queries the LLM picks from), the plan schema the LLM emits, and the validation/execution pipeline. No React, no UI, no HTTP — those live in companion packages.

Install

pnpm add @usecarte/core zod

drizzle-orm is an optional peer for the @usecarte/core/drizzle helpers; not required if you bring your own query functions.

Usage

import { defineCarte, defineEntry, generatePrompt, parsePlan, executePlan } from "@usecarte/core";
import { z } from "zod";

const carte = defineCarte([
  defineEntry({
    id: "orders.recentByCustomer",
    description: "Recent orders for a single customer",
    params: z.object({ customerId: z.string(), limit: z.number().int().max(100).default(20) }),
    returns: z.array(z.object({ id: z.string(), placedAt: z.string(), total: z.number() })),
    titleTemplate: "Recent orders for customer {customerId}",
    query: async ({ params }) => db.orders.findRecent(params.customerId, params.limit),
  }),
]);

// Build the prompt the LLM sees — no schema, no row data, no SQL.
const prompt = generatePrompt(carte, uiAdapter, ctx);

// LLM returns a JSON plan. Validate, then execute.
const parsed = parsePlan(llmJson, carte, uiAdapter, ctx);
if (parsed.ok) {
  const results = await executePlan(parsed.plan, carte);
  // results is a map: panelIndex → rows. The LLM never sees this.
}

Security model

Carte enforces three named architectural invariants — no schema in prompt, no result data in prompt or repair channel, statically-declared returns. See the security model for the full story.

More

The repo root README has the design motivation, the full request lifecycle, and a runnable 60-second SQLite tour.

License

MIT