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

@ze-norm/cli

v0.17.3

Published

Plan anything. Build anything. Turn a rough software idea into a reviewed plan, then a reviewed pull request, with Claude Code.

Readme

Plan anything. Build anything.

ZeNorm is an open-source, spec-driven development workflow for Claude Code.

Bring any software idea, however rough. ZeNorm turns it into a clear plan, then builds it, keeping the two in step to the end.

License: MIT Built for Claude Code

MIT licensed, and runs on your machine using Claude Code.

Website · Setup · Developing · Glossary

Example: one change, start to finish

Sprout is a small demo app for keeping track of when to water your houseplants. Here, ZeNorm was asked to show which plants need water today. It asked three questions, wrote a plan, built the change and opened a pull request.

The agent's work is sped up. The timer shows how long each step really took.

ZeNorm asks three questions about the idea, plans and builds it, and opens a pull request. Sprout then shows a "Due today" section with a Watered button on each plant.

Why ZeNorm

Writing code is fast now. The hard part is deciding what to build, keeping that decision from drifting, and checking the result. A chat window gives you nothing to hold on to.

  • Decisions don't get lost in chat. Every decision lands on a map, with the question, the options and who answered. The spec is written from the map, not from memory.
  • Big ideas don't fit in one prompt. A map breaks the idea into waypoints, researches your code for each, and settles them one at a time.
  • Everything is reviewed. A fresh agent reviews every spec, every ticket set and the finished work against what it was written from. Nothing ships until you say so.

Install

You need macOS or Linux (on Windows, use WSL 2), Node.js 22.14 or later, git, and Claude Code.

npm install -g @ze-norm/cli
zenorm init
zenorm run

Open http://127.0.0.1:4310, add a project, and start a map. If something's wrong, zenorm doctor tells you what. SETUP.md covers configuration, signing in without a browser, and preparing a project for delivery.

If ZeNorm is useful to you, a star on GitHub helps others find it. Want ZeNorm in the cloud for your whole team? ZeNorm Pro is coming; join the waitlist.

How it works

Point ZeNorm at a git repository on your machine (a project) and start a map for a change you have in mind. Each map moves through five stages:

| Stage | What happens | | -------------- | ------------------------------------------------------------------------------------------------------------ | | Idea | Say what you want to change, in a sentence or a page. | | Wayfinding | The agent charts a map of waypoints, researches the code, and asks you rounds of questions. | | Spec | Your decisions become a specification. An independent review checks it before you approve it. | | Tickets | The spec becomes a ticket set, reviewed the same way. | | Delivery | One run builds every ticket on a branch, runs your checks, gets a separate review, and opens a pull request. |

The screenshots below also come from Sprout. Before any code is written, the agent asks about what the idea left open, each question with a recommended answer:

A question round, answered: which plants belong in the "needs water today" section, whether they also appear in the main list, and whether a Watered tick can be undone, each answered with the recommended option

An independent review checks every spec before you approve it. On another map asking for much the same, it found that the spec never said what the list shows when no plant is due, and sent that back to you as a question:

A waypoint raised by the planning review: "List behaviour when no plant is due is unstated", decided as a "Nothing to water today" line under the heading

A delivery run implements the tickets on one branch, reruns your required checks itself, has a fresh, read-only session review the result, and opens a pull request:

A passed delivery run: both tickets implemented on the run branch, node --test rerun by ZeNorm and passed, the independent reviewer found no blocking findings, and pull request #2 is open to merge on GitHub

Everything ZeNorm plans and delivers happens in your project, on your machine. Its records stay on your machine too, in a local SQLite database.

Extending ZeNorm

Plugins can add their own server routes, UI and delivery executor. The example plugin exercises every extension point. The zenorm command runs without plugins; to compose one, run ZeNorm from a checkout (DEVELOPING.md).

ZeNorm Pro

We're building ZeNorm Pro on top of this open-source workspace. ZeNorm itself stays MIT licensed. If you'd like to hear when there's something to try, join the waitlist at zenorm.com.

Learn more

  • SETUP.md: requirements, installing, configuration and running ZeNorm
  • DEVELOPING.md: running from source, checks, tests and working on ZeNorm itself
  • CONTEXT.md: the glossary (maps, waypoints, question rounds, planning reviews)
  • skills/: the skills ZeNorm's agents follow

Acknowledgements

ZeNorm is built on the workflow from Matt Pocock's skills. A map goes from an idea to tickets the way that workflow does, using its vocabulary (Wayfinder, maps, Grilling, Research, specifications and tickets), and many of the skills ZeNorm's agents follow are adapted from that collection. ZeNorm turns that workflow into a workspace that runs on your machine.

License

MIT. ZeNorm includes skills adapted from Matt Pocock's skills and components from shadcn/ui, both under the MIT License; their notices are in THIRD_PARTY_NOTICES.md.