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

@usine/core

v0.0.1

Published

Domain model for usine: Event → Run → Step → Attempt, branded ids, the run state machine, and the typed attempt-failure taxonomy.

Readme

@usine/core

Domain model for usine, an agent-agnostic software factory: the Event → Run → Step → Attempt vocabulary every other block types against.

Everything lives in the lifecycle cluster — how one piece of work moves through the engine: a deduplicated Event opens a Run, the Run's named Step is tried as Attempts, and the state machine closes it. The attempt-channel envelope schema arrives later as a sibling cluster.

What each export is

| Export | Kind | | --- | --- | | Event, Run, Step, Attempt | Entities — the four ledger rows, identity plus validated construction | | EventId, RunId, AttemptId | Value objects — branded ids; identities that cannot be swapped for each other | | DedupKey, LoopName, StepName, AttemptNumber | Value objects — branded primitives carrying a domain constraint | | RunState.*, CancelReason, Attempt.Outcome | State value objects — discriminated unions, each state carrying exactly its own data | | RunState.awaitApproval/start/succeed/fail/retry/cancelByOperator/supersede/revoke | Typestate transitions — each accepts only the states it is legal on, so an illegal transition is a compile error | | InfraFailure, AgentFailure, RunawayFailure | Typed errors — the attempt-failure taxonomy | | AttemptFailure.isAutoRetryable, Attempt.shouldAutoRetry | Derivers — pure decision functions stating the auto-retry law (class rule; class rule capped by attempt count) |

The run state machine is pending → waiting → running → succeeded / failed / canceled, with failed → running on operator retry. The failure taxonomy separates infra failures (the only auto-retryable class, capped), agent failures (always wait for the operator), and the runaway guard tripping (never auto-retried).

Everything is 0.x: APIs change without notice while the engine grows. effect is a peer dependency — supply it yourself at the pinned version.