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

@vincemakes/kiso-web

v0.54.2

Published

kiso web: a local web app on the hosted-session service, served on 127.0.0.1.

Readme

kiso web

A local web app on the kiso hosted-session service: kiso-web runs the host in its own process and serves the page at http://127.0.0.1:4317.

npm install -g @vincemakes/kiso-web
kiso web            # or kiso-web; the terminal's `kiso` runs this package when it is installed

The host must be running for the page to work: it runs while the command runs. Node 22 or later, macOS or Linux (Windows is not supported yet); the page runs in Safari 17, Chrome or Edge. Built into the root build; typecheck, gates and proofs run here and in the Web workflow.

Development:

npm run build -w @vincemakes/kiso-web         # tsc (host, shared, state) + vite (the page into out/)
npm run start -w @vincemakes/kiso-web         # kiso-web: the host, and the default browser opened on the page
npm run gates -w @vincemakes/kiso-web         # size, deps, imports, names, paths, CJK
npm run proofs:fast -w @vincemakes/kiso-web   # daily, before each commit: no browser, no kill -9
npm run proofs:full -w @vincemakes/kiso-web   # end of a milestone, before a push, before a release
npm run check -w @vincemakes/kiso-web         # build + typecheck + gates + proofs:fast
npm run check:full -w @vincemakes/kiso-web    # the same with proofs:full

kiso-web [--port 4317] [--no-open] [--revoke-sessions]. The port is fixed, so a page added to the Dock (Safari: File > Add to Dock; Chrome or Edge: Install page as app) keeps its address. Running it again while a host holds the port opens the browser on that host; anything else on the port is an error that names the process. The host runs while the command runs: with no host, the page cannot load.

Sign-in: the command opens the browser on a one-time connect code in the address (good for two minutes); the page trades it for a session cookie (HttpOnly, SameSite=Strict, named after the port) and strips it from the address, so the page holds no secret of its own. The host keeps the sessions hashed in $KISO_HOME/web.json (mode 0600); --revoke-sessions forgets them all, and every page signs in again from the command. Every request still passes the Host and Origin checks: a cookie on 127.0.0.1 is sent to every port of it. A session is a key to this machine's shell: do not run a page you do not trust on 127.0.0.1.

Each proof is a script; its exit code is the verdict. fast is the reducer, markdown, usage, guard, sign-in, policy, control and task proofs (seconds to under a minute). full adds the ones that kill the host with kill -9 and the page proofs, which drive a headless Chrome through the DevTools protocol (Chrome is found on the machine, or named by KISO_WEB_CHROME), including a tab closed and reopened mid-run and one approval answered from two tabs. Rule: a change that only touches page styles or components needs fast; a change to src/main, src/shared, the state reducer, the transport or recovery needs full.

The model, the effort and the sign-in come from the terminal's own configuration (~/.kiso/config.json, auth.json), read through the ./config door of @vincemakes/kiso-code: one login serves both products, and no key is read from the web app's own environment. Works live where the terminal keeps sessions (~/.kiso/projects/<enc>/), so the history lists the Works of every folder. The folder a new task starts in is KISO_WEB_WORKSPACE, else the one used last while it still exists, else the home folder; another is chosen in the page's folder browser (folders only; from home, or from a full path typed in). Notifications are off until turned on in Settings, and only while the page is open. See src/main/env.ts for the rest (KISO_WEB_FAUX runs a scripted model, for the proofs).

The proofs budget (scripts/proofs) is 2,100 lines from W1c on, by an owner ruling of 2026-11-01 (it was 1,800 from W1b by a ruling of 2026-10-31, 1,600 from S5 by a ruling of 2026-10-26, 1,300 from S4 by a ruling of 2026-10-25, 1,000 from S2 by a ruling of 2026-10-23, and 700 before); the other budgets are unchanged.

Plans, mocks and screenshots live outside this repository.