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

@adysre/rules-core

v0.1.0

Published

Framework-agnostic core of the ADYSRE Business Rules Engine: AST builders, traversal and validation. No runtime dependencies.

Readme

@adysre/rules-core

The AST and everything that can be done to it: building, walking, validating, serialising, and running.

Zero runtime dependencies, deliberately. A rules engine is embedded, and one that drags a dependency tree into every bundle that touches it is one teams work around. That is also why the validator is hand-written rather than delegated to a schema library.

import { rule, all, condition, field, literal, validateRule } from '@adysre/rules-core';

const document = rule({
  name: 'Large orders need approval',
  kind: 'validation',
  when: all([
    condition({ left: field('order.total'), operator: 'greaterThan', args: [literal(1000)] }),
  ]),
  then: [action({ type: 'reject', target: 'order.total' })],
});

validateRule(document); // { valid: true, diagnostics: [] }

const evaluator = createEvaluator(createRegistry(builtinPlugins));
const { verdict, actions, trace } = evaluator.evaluate(
  document,
  createContext({ order: { total: 2500 } }),
); // 'matched', the reject action, and a record of how it got there

What is here

| Module | Purpose | | --- | --- | | builders | Construct an AST in code, with injectable ids and clock so a document is reproducible | | walk | Traverse, search, edit immutably, and report which fields, variables and plugins a rule needs | | validate | Structural validation, reporting the AST path of every problem | | serialize | Parse and stringify with a stable key order, plus a migration path between AST versions | | registry | Immutable plugin registry: duplicate ids throw at registration, lookups never throw | | builtins | 27 operators and 23 functions, offered rather than imposed | | errors | RuleError, how a plugin says "I cannot answer that" | | resolve | Operands to values: own-property field reads, bounded function nesting | | execute | The executor: verdicts, actions, diagnostics and a trace |

The renderers, the React state and the visual builder are separate packages precisely so this one is safe to import anywhere a rule has to run: a server route, a worker, a build step that lints them. Nothing here needs a DOM.

See documents/RULES_ENGINE.md.