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

@xiongxianfei/rigorloop

v0.3.1

Published

Git-first workflow for AI coding agents: proposals, specs, tests, review gates, and durable validation evidence from idea to PR.

Readme

@xiongxianfei/rigorloop

RigorLoop CLI for repository-local AI-assisted software delivery.

This package exposes the rigorloop binary for approved CLI workflows such as target initialization and change metadata scaffolding. Release archives remain verified GitHub release artifacts; they are not bundled into the npm package. npm is the CLI delivery channel, not the canonical source for workflow rules, skills, schemas, templates, or adapter archives.

Quick Start

Run directly with npx; no install step is required:

npx @xiongxianfei/rigorloop@latest --help
npx @xiongxianfei/rigorloop@latest version
npx @xiongxianfei/rigorloop@latest init codex
npx @xiongxianfei/rigorloop@latest init claude
npx @xiongxianfei/rigorloop@latest init opencode

Use a pinned version when you want reproducible setup:

npx @xiongxianfei/[email protected] init codex

Install as a project-local development dependency:

npm install --save-dev @xiongxianfei/rigorloop
npx rigorloop --help
npx rigorloop init codex

Install globally only if you want a machine-wide rigorloop command:

npm install --global @xiongxianfei/rigorloop
rigorloop --help
rigorloop init codex

Commands

rigorloop --help
rigorloop version
rigorloop init codex|claude|opencode [--write-state] [--from-archive <path>] [--dry-run] [--json]
rigorloop new-change <change-id> --title <title> [--dry-run] [--json]

Target Init

Initialize target support from the verified official release archive:

npx @xiongxianfei/[email protected] init codex --json
npx @xiongxianfei/[email protected] init claude --json
npx @xiongxianfei/[email protected] init opencode --json

Preview the write plan without mutating files:

npx @xiongxianfei/[email protected] init opencode --dry-run --json

Use --from-archive when you already downloaded the matching official archive, or when Node fetch() cannot reach GitHub from your network:

npx @xiongxianfei/[email protected] init codex --from-archive ./rigorloop-adapter-codex-v0.3.1.zip --json
npx @xiongxianfei/[email protected] init claude --from-archive ./rigorloop-adapter-claude-v0.3.1.zip --json
npx @xiongxianfei/[email protected] init opencode --from-archive ./rigorloop-adapter-opencode-v0.3.1.zip --json

Default init installs verified target support without writing rigorloop.yaml or rigorloop.lock. Use --write-state when you want RigorLoop-managed project state files. The command verifies the selected archive before extraction and verifies the installed tree before reporting success. Runtime roots are target-specific:

codex:   .agents/skills
claude:  .claude/skills
opencode: .opencode/skills and .opencode/commands when command aliases are declared

Network installs use Node fetch(). If download fails in a proxied environment, JSON output reports bounded diagnostics such as target name, release version, trusted archive URL, detected proxy environment variable names, Node env-proxy status, and failure class. It does not print proxy credentials or raw proxy values. On Node versions that support env-proxy, enable it with NODE_USE_ENV_PROXY=1, NODE_OPTIONS=--use-env-proxy, or node --use-env-proxy; otherwise use the --from-archive fallback.

Change Metadata Scaffold

Create a new change metadata scaffold:

npx @xiongxianfei/[email protected] new-change my-change --title "Describe the change" --json

Preview the scaffold first:

npx @xiongxianfei/[email protected] new-change my-change --title "Describe the change" --dry-run --json

new-change creates docs/changes/<change-id>/change.yaml. It does not claim that proposal, spec, review, verification, or PR readiness is complete.

Version Guidance

Use @latest for manual exploration. Use an explicit version such as @0.3.1 for CI, onboarding docs, and repeatable agent setup.

Source of Truth

npm is the CLI delivery channel. The canonical workflow sources, skills, specs, schemas, and release records live in the GitHub repository:

https://github.com/xiongxianfei/rigorloop