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

krafto

v0.6.0

Published

Visual editor for your existing React codebase. Click any element to edit it, or ask the AI agent — changes land in your source files as real diffs.

Readme

Krafto

Visual editor for your existing React codebase.

Click any element in your live app and edit its text and classes, or ask the AI in plain language. Your own coding agent (Claude Code / Codex) writes the change to your source as real code, committed to a krafto-owned branch — your working tree and branches are never touched.

Status: early preview. Next.js and Vite+React, macOS/Linux.

Try it

In a Next.js or Vite+React project (Node 18+):

npx krafto init   # detect the project, connect it (gitignored .krafto config)
npx krafto dev    # start the agent — open the editor from your dashboard

init doesn't rewrite your sources — it only adds the gitignored .krafto/ config and makes a single onboarding commit for it. To edit, you need a coding agent installed (Claude Code or Codex); krafto runs your own agent, never its own keys.

How editing works

Every design session lives on its own branch:

  • Opening the editor creates a session — a git worktree under .krafto/worktrees/ on branch krafto/<id>, running its own dev server.
  • An edit (an inspector tweak or an AI-panel prompt) is handed to your coding agent, which writes it to the worktree (your app hot-reloads instantly) and the change is committed to the session branch.
  • Fork a session from the editor to branch off its current state and experiment.
  • Like the look? git merge krafto/<id> whenever you want — krafto never merges or pushes for you.

The agent (krafto dev) talks to the gateway over an outbound WSS tunnel — no inbound ports, nothing deployed.

Links

License

Apache License 2.0. Copyright © Okto Labs LLP.