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

@fayz-ai/db

v0.1.2

Published

Fayz SDK database layer — Drizzle schema primitives, spine references, and migration helpers shared across plugins.

Readme

@fayz-ai/db

The shared Drizzle spine that every Fayz plugin schema composes with.

npm license

When apps are composed from plugins, their data models have to compose too. @fayz-ai/db is the schema spine: a small set of canonical Drizzle tables — tenants, persons, orders, bookings, products — plus the column helpers (tenant id, timestamps) that plugin schemas build on. Every plugin references the same spine, so a CRM's clients and an agenda's bookings agree on what a person and a tenant are.

It also re-exports drizzle-orm/pg-core so the whole stack runs on one Drizzle instance — apps compose their own tables, the spine refs, and plugin schemas without the dual-copy PgColumn type clashes you get from mismatched drizzle-orm versions.

What's inside

  • Spine tablessaasCore, tenants, persons, orders, bookings, products, orderItems (Ring 0 references plugins point at)
  • Column helperstenantId, timestamps, createdAt
  • Re-exported pg-core — the full drizzle-orm/pg-core builder surface, so every package shares one drizzle-orm instance

Install

npm install @fayz-ai/db

Depends on drizzle-orm. Import pg-core builders from here, not from drizzle-orm directly.

Usage

import { pgTable, text, tenantId, timestamps, persons } from '@fayz-ai/db'

export const notes = pgTable('notes', {
  id: text('id').primaryKey(),
  personId: text('person_id').references(() => persons.id),
  body: text('body'),
  tenantId: tenantId(),
  ...timestamps,
})

Part of the Fayz SDK

The data spine beneath every plugin schema; apps compose it in their own drizzle.config.

Roadmap & contributing

Built and evolving in the open. See the Fayz SDK roadmap for current gaps, missing features, and good first issues.