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

@actantdb/studio

v0.0.12

Published

Local UI + CLI for ActantDB: timeline, context manifest, approval, replay.

Readme

actant-studio

Local UI + CLI for Actant. Ships the actant binary.

npx actant studio                                # open the local UI
actant approve <tool_call_id> --scope once
actant deny    <tool_call_id> --reason "out of policy"
actant replay run <event_id> --without-memory mem_42
actant replay diff <run_a> <run_b>

What Studio shows

Per /examples/test-cleanup/README.md:

  • Timeline. Every captured event: model call, tool call requested, guard verdict, approval, tool result, context build, observation.
  • Context manifest detail. What was included, what was blocked, why.
  • Approval drawer. Approve / deny / constrain a pending tool call. The constrained variant is recorded.
  • Replay control. Pick an event, choose overrides (policy, memory exclusion, alternate model), run, see the side-by-side diff.

That is the scope for v0.1. Anything more is post-Gate-3.

Tech

  • React 19 + TypeScript strict.
  • Vite for the UI bundle.
  • Local Node HTTP server hosts the bundle + a websocket to @actantdb/core's ledger.
  • No remote backend. No telemetry leaving the machine by default.

Status

Pre-alpha. The Studio surface is the visible part of the killer demo and the validation tests. If the demo doesn't make sense in Studio, the demo is broken.

See /PIVOT.md, /CHANGELOG.md, /CHANGELOG.md.