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

@raniejade/rac

v0.4.2

Published

Install RAC project definitions into Claude/Codex/OpenCode config surfaces

Readme

rac

RAC keeps .rac/ as the source of truth for agent, skill, MCP, rule, and vendor-wide config definitions, then generates Claude, Codex, and OpenCode config surfaces from that source.

Use it to:

  • Install project-local config from a repository's .rac/.
  • Install user/global config from ~/.rac/.
  • Share reusable config packs across repositories.
  • Generate vendor-native outputs while keeping ownership tracked in RAC install manifests.

Requirements

  • Node.js >=20
  • npm

Project Quick Start

Project scope reads <cwd>/.rac/ and writes project-local vendor outputs.

# Scaffold .rac/ in the current project
npx @raniejade/rac init

# Validate source definitions
npx @raniejade/rac doctor

# Preview generated project outputs
npx @raniejade/rac install --dry-run

# Apply generated project outputs
npx @raniejade/rac install

User Quick Start

User scope reads ~/.rac/ and writes global/home config surfaces.

# Scaffold ~/.rac/
npx @raniejade/rac init --scope user

# Validate ~/.rac/
npx @raniejade/rac doctor --scope user

# Preview global outputs
npx @raniejade/rac install --scope user --dry-run

# Apply global outputs
npx @raniejade/rac install --scope user

For dotfiles, manage the .rac tree directly in your dotfiles repo and deploy or symlink it to ~/.rac. RAC_HOME is for relocation/testing because it changes the user-scope source home and the Claude/Codex target home; OpenCode user outputs still follow XDG_CONFIG_HOME.

Shared Packs

Project .rac/config.toml can reference shared packs:

npx @raniejade/rac pack add platform-rules github:owner/repo --ref main
npx @raniejade/rac pack list
npx @raniejade/rac install --refresh-packs --dry-run

Pack commands edit the current project's .rac/config.toml.

rac install creates .rac/rac-lock.json (committed alongside config.toml) that pins each pack to its resolved commit SHA. Subsequent installs on any machine check out the locked SHA rather than re-resolving the floating ref, so two developers and a CI job installing the same project always produce identical outputs. Use --refresh-packs to re-resolve refs and rewrite the lockfile. Use --frozen-lockfile (exit code 2 if the lockfile would change) in CI to gate on unreviewed lockfile drift. Pack overrides skip the lockfile entirely. See Lockfile for full details.

.rac/config.local.toml can add local-only packs (and local overrides). See Configuration.

Docs

  • Install Scopes: project scope, user scope, dotfiles workflow, and output paths.
  • Configuration: .rac/ layout, definition schemas, commands, merge behavior, shared packs, target outputs, and troubleshooting.
  • Architecture: internal pipeline and ownership boundaries.

Verification

docker build -f docker/smoke.Dockerfile --target smoke-test -t rac-smoke-test .