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

krow-cli

v0.3.26

Published

A document-driven workflow for coding agents

Readme

krow

krow is a harness for coding agents.

It gives agents:

  • a shared language system
  • documents that compound across work
  • a state machine that drives the work deterministically

The state machine keeps agents moving through the workflow we want instead of letting each session invent its own process.

Start

Initialize krow in a repository:

npx --yes krow-cli@latest init

Start the first session in your coding agent:

$work Add paid subscription gating to daily recommendations.

krow starts a work item. The agent reads the current language and code evidence, then may ask:

Should "Free User" mean no active subscription, or also an expired trial?
When access is blocked, should the user see an Upgrade Prompt or a disabled state?

After the user answers, the agent writes:

.krow/work/<work-id>/goal.md
.krow/work/<work-id>/spec.md
.krow/work/<work-id>/plan.md

Then it implements, verifies, writes review.md, and proposes reusable terms or system updates for approval.

Use the same surface for later work:

$work Build a habit tracking app.
$work Fix the dashboard loading bug.

What Happens

krow init creates .krow/ and installs small agent command files.

$work <request> runs:

plan -> implement -> review

The runner owns state and step order. The agent does the current step and submits evidence back to krow.

When language is missing or unclear, the agent uses repository evidence or asks the user. Approved reusable meaning goes back into .krow/system.

Files

.krow/
  system/
    glossary.md
    map.md
    docs/
  work/
    <work-id>/
      goal.md
      spec.md
      plan.md
      review.md
  state/
    workflows/

More

Design notes and implementation details live in docs/.

Development

npm install
npm run typecheck
npm test
npm run build

License

MIT