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

@eleven-am/golem-policy

v0.6.0

Published

Golem policy engine: the operator table and evaluator behind CASL condition matching, shared by the in-memory and SQL backends

Readme

@eleven-am/golem-policy

Golem's own evaluator for CASL rule conditions, replacing the @casl/prisma interpreter.

One operator table defines every supported operator once: its JavaScript predicate, its parameterised SQL rendering, its null semantics, and its operand constraints. Both backends are generated from the same entry, so the in-memory check and the database filter cannot drift apart. Only the JavaScript side is wired up today; the SQL renderings are declarative and dialect-neutral until a SQL backend consumes them.

Conditions are two-valued: an object matches a condition or it does not, and there is no third "unknown" outcome. Null and absent values are ordinary values that fail to equal things, so AND, OR and NOT are classical boolean algebra over the leaves. Numeric comparison is exact across number, bigint and Decimal, including magnitudes past Number.MAX_SAFE_INTEGER.

Unsupported operators are rejected, never approximated. validateConditions reports every offending operator with its path so an application can refuse a policy at boot instead of silently under- or over-granting at request time.

import { compileConditions, validateConditions } from '@eleven-am/golem-policy';

const result = validateConditions({ title: { contains: 'x' } });
if (!result.supported) {
  throw new Error(result.issues[0].message);
}

const compiled = compileConditions({ post: { is: { authorId: 'u1' } } });
compiled.test({ post: { authorId: 'u1' } });

See the full guide.