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

@udx/rabbit-repo

v0.1.4

Published

Repository resolution tooling for Rabbit CI

Readme

rabbit-repo

rabbit.ci resolves the GitHub delivery shape of a repository for Rabbit CI.

Run one command in a repository:

rabbit.ci

It writes .rabbit/repo.yaml with repository identity, branch rules, environments, and workflow triggers.

The generated file is committed with the code. Refresh it when GitHub delivery configuration changes.

.rabbit/context.yaml is legacy and is not read by rabbit.ci.

Status

This is the focused successor to the repository integration work that first lived in dev.kit. dev.kit remains responsible for broad generated context; Rabbit CI execution remains in its integrations and backends.

Quick start

Install the CLI globally:

npm install --global @udx/rabbit-repo

Run the command from the repository you want to resolve:

rabbit.ci
rabbit.ci --json
rabbit.ci --yaml

The default command writes .rabbit/repo.yaml and prints a short summary. --json and --yaml print the same resolution without writing a file. GitHub discovery is read-only and unavailable GitHub data is left empty. Secret and variable values are never written; only their names are included.

Resolution

The resolution contains executable repository facts:

  • branch names and effective GitHub rules;
  • organization/repository secret and variable names, plus environment-specific configuration;
  • workflow paths, triggers, and workflow-level permissions.

Read the repository resolution, repository discovery and initialization, and dev.kit migration boundary before extending it.

Development

make test

Product context

Rabbit CI helps teams own how software moves—and proves the work as it moves. Its delivery route is repository-centric, policy-governed, and evidence-producing: move fast, protect the path, craft proofs.