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

jurist

v0.0.7

Published

```sh npm i jurist ```

Readme

jurist

npm i jurist

Jurist is a TypeScript-first authorization library supporting role-based access control.

usage

Laws

With Jurist, permissions are expressed in a tree structure.

// my-authorization.ts
import { Laws, optional, required } from "jurist";

const authorization = new Laws({
  roles: ["suspended", "free", "premium"],
  permissions: required({
    create: optional({
      document: required({
        "<=5": optional({ "<=5000": null }),
        shareDocuments: null,
      }),
    }),
  }),
  rolePermissions: {
    suspended: new Set([]),
    free: new Set([
      /* a granted  permission grants all preceding permissions, e.g., 
      "create"
      "create_documents" */
      "create_documents_<=5",
    ]),
    premium: new Set([
      "create_documents_<=5_<=5000",
      "create_documents_shareDocuments",
    ]),
  },
});

The idea here is that some permissions must logically follow from other permissions. In other words, the create_documents_<=5 permission is a prerequisite for the create_documents_<=5_<=5000 permission, because if you are allowed to create 5,000 documents, you are logically allowed to create 5 documents in the first place.

This makes authorization checks easier, safer, and more explicit.

// routes.ts
import { Roles } from "jurist";

import { authorization } from "./my-authorization";
import { app } from "./my-hono-like-app";

type Role = Roles<typeof authorization>; // "free" | "premium" | "suspended"

type User = {
  id: string;
  role: Role;
};

app.post("/api/v1/resources", async (c) => {
  const { user /* { id: "123-456", role: "free" } */ } = c.get("user");
  /* ✅ true  */ authorization.check(user.role, "create");
  /* ✅ true  */ authorization.check(user.role, "create_documents_<=5");
  /* ❌ false */ authorization.check(user.role, "create_documents_<=5_<=5000");
});

Here, we can see that a free user has permission to create a resource, and has permission to own up to 5 documents, but they cannot own up to 5,000 documents like a premium user.