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

@caisson-sh/guardrails

v0.5.2

Published

Content-safety layer: swappable Moderator port (local | provider | custom) + TS-native PII engine (mask / hash / reversible-tokenize via field-crypto) behind a fail-closed input/output guard.

Readme

@caisson-sh/guardrails

A content-safety layer for AI features: moderate input and output text, redact or reversibly tokenize PII, and block anything that looks like a leaked credential — all fail-closed by default, so an outage blocks a call instead of silently letting it through unchecked.

  • Layer: base

What it gives you

  • guardInput / guardOutput — the enforced chokepoint around a model call. A blocked input throws before the call ever happens (no spend, no round-trip); a blocked output throws after, still visible to the caller as a typed error rather than a silent pass-through.
  • A swappable moderator. Three drivers ship out of the box: local (a zero-network regex denylist, the cheap default), provider (wraps an injected moderation check), and custom (your own hook). Fail-closed by default — a moderator timeout or outage blocks the call unless a policy explicitly opts into fail-open.
  • An unconditional secret-shape pre-screen. Runs before the moderator on every call, independent of policy — text that looks like a credential (an API key, a token) is blocked regardless of what the moderator would say.
  • A PII engine. detectPii / redactPii find and mask common PII kinds; tokenizePii / detokenizePii do the same reversibly — the model only ever sees an opaque placeholder, and the original value is restored for the caller afterward from an encrypted context.
  • A dark-pattern evaluator for marketing copy. evaluateFtc4P scores static UI/marketing text against the FTC's "4 Ps" presentation dimensions (an evaluator you run at copy-review time, not a live request-path check).
  • A claim-ceiling gate. assertClaimAllowed / claimTier check a marketing or product claim string against the evidence backing it, so a claim can't outrun what's actually been measured.

Usage

import {
  guardInput,
  guardOutput,
  localModerator,
} from "@caisson-sh/guardrails";

const policy = {
  policyName: "default",
  moderator: localModerator(["forbidden phrase"]),
};
const runtime = { tenantId: accountId, sink: eventSink };

const { text: safeInput, tokens } = await guardInput(userText, policy, runtime);
// ... send safeInput to the model ...
await guardOutput(modelReply, policy, runtime); // throws if the reply is flagged

Test

bun test packages/guardrails/src