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

autonomation

v0.0.1

Published

Operating doctrine for multi-agent software factories — Toyota Production System and TSMC manufacturing principles translated into artifacts for agentic engineering.

Readme

autonomation

Operating doctrine for multi-agent software factories. Toyota Production System and TSMC manufacturing principles translated into artifacts for agentic engineering — schemas, halt conditions, gates, yield dashboards, and rituals that turn a capable agent substrate into one that ratchets every cycle.

Status: v0.0.1 — early scaffolding. The conceptual frame is in place; implementation surfaces are built incrementally.

What this is

Autonomation is the doctrine layer for the swarmkit ecosystem. It is not a runtime, learning system, memory layer, or task tracker — those already exist in macro-agent, cognitive-core, minimem, opentasks, and friends. Autonomation supplies the discipline layer those components are missing: explicit halt signals, structured failure taxonomies, yield decomposition, signal-driven kaizen, externalization-as-closure protocols, and standardized work contracts.

The framing target is a dark factory — multi-agent swarms producing software with minimal human-in-the-loop, where every TPS principle that used to be carried by human attention has to be carried by an artifact instead.

Surfaces (planned)

| Surface | Purpose | Status | |---|---|---| | doctrine/ | Cultural layer in artifact form — TPS/TSMC principles with carriers | initial | | standards/ | Schemas, taxonomies, role contracts (poka-yoke + standardized work) | next | | halts/ | Andon condition library + halt-signal schema (jidoka) | planned | | gates/ | Promotion + eval policies (jidoka + disciplined cadence) | planned | | yield/ | Metrics, queries, dashboards (yield obsession) | planned | | rituals/ | Retrospective, trace-walk, tournament, skill-harvest workflows (kaizen) | planned | | playbooks/ | Packaged standardized work | deferred until friction data exists |

See DESIGN.md for the build order with stop-conditions per phase.

Install

npm install autonomation

License

MIT