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

jsonspecs-cli

v1.1.0

Published

CLI backend and local studio host for jsonspecs rules projects

Readme

JSONSpecs CLI

CI npm License: MIT Node 20+

CLI backend and local studio host for jsonspecs rules projects.

Commands

  • jsonspecs init <project-name>
  • jsonspecs studio
  • jsonspecs validate
  • jsonspecs build

Studio architecture

jsonspecs-cli serves a built SPA from / and exposes a JSON API under /api/*. The current bundled frontend is expected to be built from the separate jsonspecs-studio-ui project and copied into static/.

Runtime model

jsonspecs-cli is an authoring/build tool. It works with a rules project that contains:

  • source rules in rules/
  • project metadata in manifest.json
  • project-local Node operator packs in operators/node
  • sample payloads in samples/

Custom operators

Project-local custom operators are loaded from manifest.json:

{
  "operatorPacks": {
    "node": ["./operators/node"]
  }
}

A local node operator pack should export an object with check, predicate and optional meta sections:

module.exports = {
  check: {
    amount_gt_zero(rule, ctx) {
      const got = ctx.get(rule.field);
      if (!got.ok()) return { ok: false, actual: undefined };

      const n = Number(got.value);
      return { ok: Number.isFinite(n) && n > 0, actual: got.value };
    },
  },
  predicate: {},
  meta: {
    operators: {
      amount_gt_zero: {
        description: "должно быть больше нуля",
      },
    },
  },
};

Stable operator context

Custom operators should use the runtime context passed by jsonspecs:

  • ctx.get(path) — reads a payload field in a stable way
  • ctx.has(path) — checks field presence
  • ctx.payload — raw payload map
  • ctx.getDictionary(id) — access a dictionary by id

Project-local operator packs should not import deepGet or jsonspecs directly.

Install

npm install
npm link

Test

npm test