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

chekd

v0.1.0

Published

The verification cockpit for apps your AI wrote. npx chekd <url> walks your app in a real browser, catches dead/broken/ugly findings as correctable cards, and learns your taste. Local-first, BYO model, nothing uploads.

Downloads

324

Readme

chekd™

The verification cockpit for apps your AI wrote.

npx chekd http://localhost:5173

Replace the URL with your own running app — type the address bare, no angle brackets.

Paste one line. In a couple minutes you're walking your own app — catching the dead, broken, and ugly, correcting the AI's take, and teaching chekd your taste. Your builder cheks* its own homework.

* chek = check · chex = checks · chekd = it's been checked

Quick start

# one-time: chekd drives a real browser (Playwright's Chromium)
npx playwright install chromium

# then chek anything
npx chekd http://localhost:5173    # a running app
npx chekd ./my-app                 # a repo — boots its own dev server, then walks it
npx chekd ./site-folder            # a static folder (page.html and file:/// work too)

chekd walks your app in a real browser, probes every control it can find, then opens the cockpit in your browser (a local server on 127.0.0.1 — nothing leaves your machine). Findings arrive as cards you can act on: fix · dismiss · snooze. Dismissals are remembered — the next chek is quieter where you said it should be.

No account. No upload. No config to wade through.

…or paste it to your coding agent: "run npx chekd on this app and walk me through what's broken."

Run the local build (this repo)

npx chekd installs the published package. To run the code in this repo instead — no publish needed:

# from inside this repo — runs the real local build, no publish needed
npm install
npx playwright install chromium   # one-time
npm run chekd -- http://localhost:5173

The -- is required so npm forwards the URL to the script. (npx chekd <URL> runs the published package; npm run chekd -- <URL> runs the code in this repo.)

What a chek catches

  • Dead and broken controls — buttons that do nothing on click, handlers that throw, links that go nowhere. Model-free and $0, every run.
  • Content slop — mojibake/encoding artifacts, leaked i18n keys, stray undefined/NaN in visible text. Also $0.
  • Design & taste observations (optional) — when a free model is available (the claude CLI on your PATH, or a local Ollama vision model), chekd reads the walk's screenshots and offers observations, never verdicts. Tell it "that's my style" once and it stops mentioning it.

Fix it for real (FULLFIX)

Bind your source repo and the cockpit's Fix it writes a real fix to a qa/<runId> branch — main never moves, nothing is merged for you:

npx chekd http://localhost:5173 --repo ./my-app

Run npx chekd ./my-app (the repo form) and the repo is bound automatically. Bindings are remembered per app.

Bring any model. Nothing uploads.

  • The objective walk is model-free and $0 — it never needs a key, a login, or a model.
  • The taste pass is BYO-model: it prefers a subscription you already have (e.g. the claude CLI), offers a free local model (Ollama), and accepts a paid key — all offered, none forced. Metered billing is never auto-selected; opt in and chekd triple-checks first and points you at the free options.
  • Local-first: your findings, corrections, and screenshots stay on your machine (in a .chekd/ folder). The only thing that can ever leave is the AI request you choose, to your provider. Run a local model and nothing leaves at all.

AS IS — review before you merge

chekd is provided "AS IS", without warranty of any kind (Apache-2.0 §7–8 + DISCLAIMER.md). Its findings and proposed fixes can be wrong — review every fix before merging: chekd writes only to an isolated qa/<runId> branch in your repo; it never touches main, never merges, and never pushes. If you point chekd at a paid provider, you run your own CLI / API key under your own account and that provider's Terms of Service — chekd never resells, proxies, stores, or meters your usage.

Requirements

  • Node.js 18+
  • A one-time npx playwright install chromium (chekd will tell you if it's missing)

License

Apache-2.0. "chekd" and the chekd logo are trademarks of John Kilfoil — the Apache-2.0 license does not grant trademark rights (see NOTICE).


Website: chekd.net · For AI agents consuming chekd programmatically, see docs/agent-usage.md in the repository.