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

@houserules/payload

v0.2.2

Published

houserules: shared payload libraries, copied into .claude/scripts/lib and executed on bare node with zero runtime dependencies.

Readme

@houserules/payload

The shared libraries that back houserules's installed hooks: reading houserules.config.json, reading and writing the backlog/decision ledgers, listing workspace packages, and running child processes. Every one of them ships with zero runtime dependencies, node builtins only, because they are copied byte for byte into a user's .claude/scripts/lib/ and executed there on bare node.

This package is not a plugin. It contributes no modules and is never installed directly. @houserules/cli depends on it directly, copying these libs alongside every hook script that imports one, and any first-party or third-party plugin that needs one of them imports it by package name:

import { loadConfigSafe } from '@houserules/payload/config';

That import never reaches the published .mjs. @houserules/cli's payload build rewrites it to a relative path pointing at a copy of the lib placed alongside the importing script, which is what keeps the installed hook dependency-free.

Part of houserules

houserules is portable Claude Code infrastructure that keeps the agent's context lean. The package list has the rest.

License

MIT. See LICENSE.