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

@criterionx/server

v0.3.5

Published

HTTP server for Criterion decisions with auto-generated docs

Downloads

599

Readme

@criterionx/server

HTTP server for Criterion decisions with auto-generated documentation.

The server is a delivery mechanism, not a decision engine.

Installation

npm install @criterionx/server @criterionx/core zod

Quick Start

import { createServer } from "@criterionx/server";
import { defineDecision } from "@criterionx/core";
import { z } from "zod";

const riskDecision = defineDecision({
  id: "transaction-risk",
  version: "1.0.0",
  inputSchema: z.object({ amount: z.number() }),
  outputSchema: z.object({ risk: z.enum(["HIGH", "LOW"]) }),
  profileSchema: z.object({ threshold: z.number() }),
  rules: [
    {
      id: "high-risk",
      when: (input, profile) => input.amount > profile.threshold,
      emit: () => ({ risk: "HIGH" }),
      explain: (input, profile) =>
        `Amount ${input.amount} exceeds threshold ${profile.threshold}`,
    },
    {
      id: "low-risk",
      when: () => true,
      emit: () => ({ risk: "LOW" }),
      explain: () => "Amount within acceptable range",
    },
  ],
});

const server = createServer({
  decisions: [riskDecision],
  profiles: {
    "transaction-risk": { threshold: 10000 },
  },
});

server.listen(3000);
// Server running at http://localhost:3000
// Docs at http://localhost:3000/docs

Endpoints

| Method | Path | Description | |--------|------|-------------| | GET | / | Health check | | GET | /docs | Interactive documentation UI | | GET | /decisions | List all registered decisions | | GET | /decisions/:id/schema | JSON Schema for decision | | POST | /decisions/:id | Evaluate a decision |

API

createServer(options)

Creates a new Criterion server.

interface ServerOptions<TDecisions> {
  decisions: TDecisions[];
  profiles?: Record<string, unknown>;
  port?: number;
  cors?: boolean;
}

POST /decisions/:id

Evaluate a decision with the given input.

Request:

{
  "input": { "amount": 15000 },
  "profile": { "threshold": 10000 }
}

Response:

{
  "status": "OK",
  "data": { "risk": "HIGH" },
  "meta": {
    "decisionId": "transaction-risk",
    "decisionVersion": "1.0.0",
    "matchedRule": "high-risk",
    "explanation": "Amount 15000 exceeds threshold 10000",
    "evaluatedAt": "2024-12-29T12:00:00.000Z"
  }
}

Design Principles

  1. Server does NOT add decision logic — only calls engine.run()
  2. Decisions are explicitly registered — no auto-discovery
  3. UI cannot invent defaults — shows exactly what's required
  4. JSON Schema is primary — OpenAPI is derived

Documentation

Full documentation: https://tomymaritano.github.io/criterionx/

License

MIT