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

@corgod/kept-cli

v0.1.1

Published

KEPT CLI — build, verify, reconcile, evolve, amend, snapshot, handoff, doctor.

Readme

@corgod/kept-cli

The kept command. KEPT graphs every claim your product makes about itself, cites each one to the file and line that states it, binds each to a Kane CLI test, and publishes the verdicts. You cannot break what was never proven to work.

npm install -g @corgod/kept-cli

Commands: init, build, verify, reconcile, evolve, amend, snapshot, handoff, doctor.

Prerequisites

  • Node 20.19.4 or newer.
  • Kane CLI on your PATH, authenticated with your own account. See the section below.
  • A local Chrome. Kane drives a real browser to earn a verdict, which is why no hosted service can run this for you.

Bring your own Kane credentials

KEPT ships no keys, stores no keys and reads none of yours. It never bundles, installs or vendors kane-cli: it spawns whatever is on your PATH and parses the NDJSON that binary writes. Authentication, billing and credit consumption are entirely between you and Kane, and Kane is what bills. Nothing you install from npm here can spend anything.

So install and log in to Kane yourself, following Kane's own documentation:

npm install -g kane-cli     # or however Kane distributes it for you
kane-cli --version          # KEPT is developed against 0.8.4
kane-cli login              # your account, your credits

Then confirm KEPT can see it:

kept doctor

Check 1 reports the resolved binary path and the version it answered with. If it reports the binary missing, that is a supported state rather than a crash, and the check names the remedy.

Without Kane authenticated you still get most of the product, which is deliberate:

| Command | Without Kane | |---|---| | kept init | works fully, zero invocations | | kept doctor | works fully, reports Kane as missing with a remedy | | kept build | works: reads your documents, cites them, binds designed tests. The coverage axis is withheld rather than reported as zero, and the graph says so | | kept snapshot | works, writes the ledger from whatever the graph honestly holds | | kept verify | needs Kane. This is the command that earns verdicts and spends credits | | kept reconcile, kept evolve | need Kane |

That split is the point. A graph with no verdicts tells you what you have promised and what you owe; it simply refuses to claim anything was proven. Authenticating Kane is what turns the owed column into an earned one.

First step

kept init

kept init scaffolds the KEPT config and the designed-test corpus in the repository you run it in. It is idempotent: run it twice and the second run writes nothing. Everything else assumes it has run.

Then:

kept doctor      # what is present, what is missing, and the remedy for each
kept build       # read the claims, cite them, bind the designed tests
kept verify      # spawn Kane, route the verdicts
kept snapshot    # write the ledger snapshot

kept doctor is safe to run first and costs nothing: it probes Kane once on a 10-second budget and spends zero credits.

License

MIT.