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

humanctl

v0.1.0

Published

A control plane for the human bottleneck.

Downloads

105

Readme

humanctl

humanctl is a control plane for the human bottleneck.

When agents get blocked on human context, feedback, approval, or missing taste, humanctl gives them a better surface to escalate, show, ask, and resume. Instead of scattering HTML files, screenshots, side notes, and half-answered questions across chat threads, agents can write to a shared local surface with durable state.

Why this exists

Current human-in-the-loop workflows are usually bad in the same predictable ways:

  • chat is linear and thread-local
  • previews are disposable
  • feedback arrives out of band
  • active sessions miss updates
  • future sessions have to reconstruct context from scraps

humanctl is meant to fix that with a local-first model:

  • agents write rich artifacts and requests into .humanctl/
  • humans respond through a shared surface instead of a single chat thread
  • updates are persisted to files and also emitted as events
  • active sessions can consume those updates as steers
  • future sessions can resume from the same durable state

Core thesis

Humans are scarce reviewers, not infinitely available chat partners.

humanctl helps agents package blockers into the smallest possible unit of human attention, keep all supporting context attached, and resume immediately after the answer lands.

V1 scope

The first version stays deliberately small:

  • a project-local .humanctl/ workspace on disk
  • tabs as the main navigation unit
  • things as flexible renderable objects
  • an append-only event queue for steers and answers
  • a local app surface that can render HTML, markdown, images, diffs, files, and forms
  • a tiny CLI that agents and automations can write to

Repo layout

humanctl/
  .humanctl/
  bin/
    humanctl.js
  docs/
    v1.md
  src/
    app/
      globals.css
      layout.tsx
      page.tsx
  project.dgkit.json
  next.config.ts
  tsconfig.json
  package.json
  README.md

Local preview

cd /Users/danielgwilson/local_git/humanctl
npm install
npm run dev

This starts the Next.js app locally. The CLI workspace is still separate and lives in .humanctl/.

Current CLI

The CLI is intentionally tiny right now:

  • humanctl init [dir]
  • humanctl status [dir]
  • humanctl serve [dir] --port 4173

init creates a starter .humanctl/ workspace. status summarizes what is there. serve remains available for simple static previews, but the main app now runs on Next.js.

Next milestones

  1. Finalize the .humanctl/ object model and event schema.
  2. Build the first real app surface around tabs, asks, and artifacts.
  3. Add agent-first commands for ask, put, watch, and focus.
  4. Support live steer delivery on top of the persisted queue.

Product line

humanctl: a control plane for the human bottleneck.

License

humanctl is licensed under Apache-2.0. See LICENSE.

Contributions

Unless explicitly agreed otherwise, submitted contributions are expected to be made under the same Apache-2.0 terms as the rest of the project.