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

@ai-matrx/api

v0.1.36

Published

The one way every app talks to every AI Matrx server: generated from the server contract, split by domain so an app loads only the requests it calls. Transport, five credential kinds, organization binding, streams, job follow. No screens, app state or dat

Readme

@ai-matrx/api

The one way every app talks to every AI Matrx server. Generated from the server contract and split by area, so an app only loads the requests it calls. It never holds screens, app state or database code.

import { createApi } from "@ai-matrx/api";
import { listAssets } from "@ai-matrx/api/files";

const api = createApi({ credentials: { kind: "api_key", apiKey: process.env.MATRX_API_KEY! }, organizationId });
const page = await listAssets(api, { query: { limit: 50 } });
  • Credentials — one setting: a credential, a getter, or a CredentialsPort (user, guest, api_key, service, scoped).
  • Organization — bound once; sent per each operation's contract rule (required / optional / exempt).
  • Routing — each operation knows which deployment answers; override with baseUrls or resolveBaseUrl.
  • Streams — NDJSON/SSE operations return an async iterable; *_or_json operations return { kind: "json" } | { kind: "stream" }.
  • Sections — @ai-matrx/api/<domain> per domain, /schemas, /types (type-only components/paths view), /stream, /net, /credentials. Importing one domain loads no other domain's code.

Regenerate after a server contract change: node scripts/generate.mjs (input: aidream api-contract/). --check fails on drift.

Gates

pnpm check:package runs the generator --check, the build, exports agreement, publint and the section probe (scripts/section-probe.mjs: no domain section loads another domain's code; one imported operation bundles exactly one operation descriptor).