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

@adjudicate/primitives

v0.3.0

Published

Layer 2 risk primitives — generic guard + taint factories that two or more Packs already share. Sits between @adjudicate/core (Layer 1, kernel) and per-domain Packs (Layer 3).

Readme

@adjudicate/primitives

Layer 2 risk primitives — generic guard + taint factories shared by two or more Packs. Sits between @adjudicate/core (Layer 1, kernel) and per-domain Packs (Layer 3). Each factory runs at Pack-definition time and returns a tight, kernel-direct Guard / TaintPolicy.

Guard factories

| Factory | Emits | Use | |---|---|---| | createThresholdGuard | any | numeric crossing → caller-supplied Decision | | createConfirmGuard | REQUEST_CONFIRMATION | numeric crossing → confirmation prompt | | createEscalateGuard | ESCALATE | numeric crossing → human/supervisor | | createRewriteGuard | REWRITE | clamp a numeric payload field to a cap | | createStateDeferGuard | DEFER | park an intent on a wire signal | | createIdempotencyGuard | REFUSE | domain-level dedup (not the ledger) | | createDataClassificationGuard | REWRITE / REFUSE | scan payload for PII/PHI and redact or block | | requireTenantBinding | REFUSE | reject actors not bound to the tenant in state |

Taint factories

| Factory | Returns | Use | |---|---|---| | createSystemTaintPolicy | TaintPolicy | require TRUSTED for an allowlist of system-only intent kinds |

createDataClassificationGuard (ADR-117)

import { createDataClassificationGuard } from "@adjudicate/primitives";

const redactPii = createDataClassificationGuard({
  matches: (env) => env.kind === "support.ticket.create",
  patterns: [
    { id: "ssn", pattern: /\b\d{3}-\d{2}-\d{4}\b/ },
    { id: "pan", pattern: /\b\d{16}\b/ },
  ],
  scannedFields: ["subject", "body"], // dotted paths; required + non-empty
  action: "REWRITE", // or "REFUSE"
  sensitivityLevel: "high",
});
  • REWRITE masks the matched substrings in the matched fields and re-emits the envelope with the redacted payload. Taint is preserved verbatim — redaction removes content but never declassifies (so it can never trip rewrite_taint_regression).
  • REFUSE blocks the intent with a SECURITY refusal.
  • The runtime sensitivityLevel + redactedFields ride in DecisionBasis.detail (the only structured channel that reaches the AuditRecord); the static GuardDescription.data_classification carries the permitted scope for analyzers. Both, by design.

Pure: regex evaluation over envelope.payload, no clock/I/O/RNG. @experimental until Pack feedback per the L2 freeze convention.