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

kaya-editor

v0.1.1

Published

Local browser review surface for agent-written artifacts. Annotate, send feedback, no upload.

Readme

KAYA Editor

Review an HTML or Markdown artifact in your browser, annotate it, and send the feedback back to the agent that wrote it. Everything runs on your machine.

No account, no upload, no third-party host. A dependency-free Node server that serves one file and injects a review overlay over it.

npm i -g kaya-editor

kaya plan.html            # open a review session, prints a local URL
kaya poll plan.html       # wait for the feedback you queue in the browser
kaya export plan.html     # write a self-contained copy that opens with no server
kaya end plan.html        # close the review

What it is for

An agent writes a document — a plan, a report, a spec, a comparison. Reading that in a terminal is miserable and reviewing it in prose is worse. KAYA serves the artifact as a page you can actually look at, lets you attach notes to specific elements, and hands those notes back to the agent as structured feedback.

The loop: agent writes → you annotate → agent revises → repeat, until you end it.

Commands

| Command | What it does | |---|---| | kaya <file> | Open or resume a review. Prints the URL and opens a browser. | | kaya <file> --reopen | Reopen a review you ended. Required — see below. | | kaya poll <file> [--agent-reply "..."] | Block until you send feedback or end the session. | | kaya export <file> [--out <path>] | Write a standalone HTML copy with local assets inlined. | | kaya end <file> | End the review as the agent. | | kaya list | Show active sessions. | | kaya stop [file] | Stop the server. |

Markdown is rendered to a dark themed page for review. The source file is never rewritten, so tooling that parses your raw Markdown keeps working.

In the browser

  • Annotate — toggle it on, click an element or select text, write a note. Notes queue up; send them as one batch.
  • Zoom — hover a diagram, image or SVG for a zoom control. Wheel to zoom, drag to pan. With Annotate on, click a node inside the zoom to comment on it.
  • Conversation — the agent's replies and your notes, in order.
  • Layout issues — flags when the page scrolls sideways. Containers that scroll on purpose are not flagged.

Notes survive a reload

Queued notes are staged in sessionStorage and restored automatically, so a reload, a crash, or an accidental navigation does not destroy work you have typed. Staging is cleared only after a send succeeds.

Sessions you end stay ended

If you end a review from the browser, a plain kaya <file> refuses to reopen it and says so. An agent cannot wander back into a review you closed; it has to be asked, via --reopen. An agent ending its own turn does not lock you out.

Asking you a question

An artifact can declare a question and KAYA renders the control:

<div data-kaya-ask="approach"
     data-kaya-label="Which approach?"
     data-kaya-options="rewrite|patch|leave it"></div>

Clicking an option queues [ask] approach = patch. Because KAYA owns the widget, the answer comes back typed instead of as prose the agent has to interpret.

Requirements

Node >= 22. No runtime dependencies.

Assets

KAYA serves the file through a local server rooted at that file's own directory. Put images, CSS and fonts alongside the artifact and reference them with relative paths — never a leading /.

Licence

FSL-1.1-MIT — source-available now, converts to plain MIT two years after each release. See LICENSE for the full terms and THIRD-PARTY-NOTICES.md for attribution.