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

dark-kitchen

v0.3.0

Published

Autonomous coding agent control plane — connects trackers, git, coding agents, and human channels

Readme

dark-kitchen

The npm CLI for Dark Kitchen, a self-hosted control plane that turns tracker tasks into isolated agent workflows, verified GitHub pull requests, and durable human interventions.

Dark Kitchen is pre-1.0. Pin a reviewed version, keep GitHub required checks/approval enabled during commissioning, and run a live smoke with your exact tracker, harness, model, and messaging credentials before unattended use.

Requirements

  • Node.js 22.13 or later and Git.
  • An existing Git repository with an origin remote.
  • Tracker and GitHub SCM credentials in environment variables.
  • An installed/authenticated ACP agent such as Codex or OpenCode. The compatible acpx runtime is included.

Quick start

From the existing project root:

npm install --save-dev --save-exact [email protected]
npx dark-kitchen init

Edit .dark-kitchen/config.yaml, then:

export GITHUB_TOKEN='...'
npx dark-kitchen doctor
npx dark-kitchen start --foreground

init creates the config only when it is absent and does not replace unrelated files. The built-in workflow maps semantic roles (implementer, reviewer, fixer, repository-tester, optional verifier) to your selected harness profiles and keeps one primary Git worktree per active task.

Human messaging is optional. Telegram is included and iMessage uses the macOS host. Discord, Slack, and WhatsApp are opt-in peers: install [email protected], @slack/[email protected], or [email protected] beside this package only when enabling that channel. WhatsApp additionally needs QR pairing. DeepSeek Harness is user-managed and currently has an upstream rc.8 dependency-resolution caveat documented in the repository.

Security and operations

  • Put token environment-variable names in YAML, never token values.
  • Keep the daemon MCP endpoint on loopback unless an authenticated/allowlisted HTTPS boundary is configured.
  • Treat project workflow files, harness plugins, and injected MCP servers as executable authority.
  • Keep branch protection and exact required check names enabled.
  • Back up .dark-kitchen/runtime and managed tool state before upgrades.

Full documentation: