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

repo-context-kit

v1.9.0

Published

Compact deterministic repository runtime for AI coding agents.

Readme

repo-context-kit

Compact deterministic repository runtime for AI coding agents.

repo-context-kit is MCP-native first: MCP transport + runtime/v1 JSON state + minimal CLI fallback.

Primary interfaces:

  1. MCP (rck-mcp)
  2. runtime/v1 JSON (.aidw/runtime/*.json)
  3. minimal CLI (rck)

It provides bounded repository context, runtime task state, verification framing, and confirmation-gated execution for AI coding agents.

MCP

rck-mcp --root <repo>

The MCP server is read-only by default. Write, test, and external-side-effect tiers require explicit opt-in and still honor the confirmation gate.

Runtime

JSON is the source of truth:

  • .aidw/runtime/task.json
  • .aidw/runtime/context.json
  • .aidw/runtime/execution.json
  • .aidw/runtime/verification.json

Markdown is a readable view only.

Usage

Default workflow:

rck init
rck scan
rck doctor
rck check
rck task prompt <taskId>
# human implementation
rck task checklist <taskId>
rck task pr <taskId>
rck scan --check
rck check --strict

Preflight for local or CI usage:

rck scan --check
rck check --strict
  • scan --check verifies generated context and runtime JSON freshness.
  • check --strict evaluates governance signals without writing files.
  • scan --auto is a managed refresh mode for gated/MCP flows. It is not the default human workflow.
  • doctor explains setup, freshness, and PDGL readiness when something feels off.

Command reference:

rck init
rck init --dry-run
rck init --force
rck init --force --update-agent-files
rck scan [--check]
rck scan --auto
rck doctor
rck install-status
rck version --paths
rck context brief
rck context next-task
rck context workset <taskId>
rck task prompt <taskId>
rck task checklist <taskId>
rck task pr <taskId>
rck gate status
rck gate reset
rck gate confirm task <taskId>
rck gate confirm task <taskId> --ttl-minutes <n> --json
rck gate confirm tests <taskId>
rck gate confirm tests <taskId> --json
rck gate run-test <taskId> --token <token>
rck gate run-test <taskId> --token <token> --json
rck check [--explain]
rck check [--strict | --warn-only]
rck metrics

Use rck <command> --help for command-specific options.