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

@cairnkit/cli

v0.12.4

Published

cairnkit check — fails the build when a tour points at UI that no longer exists.

Readme

@cairnkit/cli

cairnkit check — fails the build when a tour points at UI that no longer exists.

npm i -D @cairnkit/cli
"scripts": { "lint": "eslint . && cairnkit check" }

Getting set up

npx cairnkit init

Detects your framework and scaffolds anchors, a flow, the typed registry and a provider. It never overwrites a file and never edits your layout — it prints that step instead. --dry-run shows the plan; --dir chooses where files go.

Checking

Run it directly with npx, since the binary is a local dev dependency rather than a global one:

npx cairnkit check                    # defaults to src
npx cairnkit check src app            # several roots, scanned as one project
✗ cairnkit check failed

  • 1 anchor(s) are registered but never applied to an element  [anchors-applied]
      - questions.save  (breaks "create-questions")  src/walkthrough/flows.ts:35
      Spread {...anchor(...)} on the element, or remove the anchor and the step pointing at it.

Describing what is there

check answers "is anything wrong". status answers "what is there": every anchor, whether an element carries it, where it was declared, and which flows point at it. It always exits 0, because describing a project is not a verdict on it.

npx cairnkit status                   # readable
npx cairnkit status --json            # the anchor graph, for tooling

--json works on both commands. In that mode stdout carries exactly one JSON object and every human-facing message goes to stderr, so it pipes straight into a parser:

npx cairnkit check --json | jq '.findings[].detail[].at'

The payload carries a version field. It is a contract the moment anything consumes it, and a consumer needs to tell an old shape from a new one without guessing from which keys happen to be present.

What it checks

  • Every registered anchor is applied to a real element
  • Every data-cairn in the codebase is in the registry
  • No route is both a pause route and a handoff route, and no flow hands off to itself

Runs in about a second, reads text only, and never imports or executes your project code.

Full documentation: cairnkit.dev

MIT