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

@porulle/db

v0.10.4

Published

The database surface plugins use instead of importing Drizzle directly.

Readme

@porulle/db

The database surface plugins use instead of importing Drizzle directly.

import { defineTable, column, eq, and, sql } from "@porulle/db";

Why this exists

If every plugin imported from drizzle-orm directly, the framework couldn't:

  • Inject organizationId and id columns automatically
  • Add the standard createdAt / updatedAt timestamps
  • Generate the per-org index + composite unique constraints
  • Hot-swap the underlying ORM if we ever needed to (today: Drizzle on PostgreSQL — tomorrow could be different)

@porulle/db is the thin contract that decouples plugins from the ORM. Drizzle stays as an implementation detail.

API

defineTable(name, columns)

Top-level table. Auto-injects: id (UUID PK), organizationId (text NOT NULL with org index), createdAt and updatedAt (timestamps).

import { defineTable, column } from "@porulle/db";

export const giftCards = defineTable("gift_cards", {
  code: column.text({ unique: true }),
  balance: column.integer(),
  status: column.text({ enum: ["active", "disabled"], default: "active" }),
});

column.* builders

column.text({ unique?, optional?, enum?, default? }) column.integer({ optional?, default? }) column.boolean({ default? }) column.timestamp({ optional? }) column.jsonb<T>({ optional?, default? }) column.uuid({ optional?, default? }) — for FKs to other org-scoped tables (child tables skip the auto-org column)

Re-exported Drizzle operators

For query construction without importing drizzle-orm directly:

eq, ne, gt, gte, lt, lte, and, or, not, like, ilike, notLike,
inArray, notInArray, isNull, isNotNull, between, sql, desc, asc

Conventions

  • Every top-level table is org-scoped via the auto-injected organizationId. Cross-tenant queries are a closed surface — see SECURITY.md.
  • Child tables (FK to a parent that already carries organizationId) get id and createdAt only. The parent's org column protects the child rows.
  • Drizzle hash drift across workspace copies has bitten us before — @porulle/db re-exports the operators so plugins inherit a single drizzle version.

See also

  • Plugin Contract — Drizzle-first rule + org-scoping requirement
  • packages/core/src/kernel/database/ — how the kernel composes the schema