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

@loopyc/operator

v0.9.0

Published

Local-first operator, journal read model, scheduler, and control center for Monkey D Loopy.

Readme

@loopyc/operator

The local-first Monkey D Loopy operator. The initial surface is a zero-mutation read model over existing runtime journals; the loopback API, control center, scheduler, and guarded controls build on the same derived state.

Install the CLI globally, or add the package to an application that uses the read-model API:

npm install --global @loopyc/operator
# or: npm install @loopyc/operator
import { readRun, listRuns } from "@loopyc/operator";

const run = readRun("/path/to/standalone-artifact", "default");
console.log(run.status, run.integrity, run.source.events);

events.jsonl remains the source of truth. Inspection verifies the checksum chain, derives state from committed events, never acquires the runtime lock, and never rewrites old journals. Torn tails, corruption, truncation, uncertain effects, live locks, and newer schemas are visible and cannot be reported as healthy.

loopyd install ./out/my-loop/standalone   # import only; artifact remains independent
loopyd handoff my-loop operator --reason "host timer disabled"
loopyd step my-loop --run-id check-1
loopyd pause my-loop --run-id check-1 --reason "maintenance"
loopyd resume my-loop --run-id check-1 --reason "maintenance complete"
loopyd evolve propose my-loop ./candidate.loop.yaml
loopyd evolve approve my-loop <candidate-id> --reason "reviewed gates and fixtures"
loopyd evolve rollback my-loop --reason "restore known-good revision"
loopyd up --background                    # macOS/Linux detached local process
loopyd status
loopyd snapshot                           # compact authenticated JSON for local control surfaces
loopyd control my-loop step               # route an action through the running operator
loopyd ui                                 # print the token bootstrap URL
loopyd down                               # graceful local shutdown

Windows supports loopyd up in the foreground; the CLI fails with an explicit diagnostic for background mode. The service binds only to loopback, authenticates every route, exchanges the tokenized bootstrap URL for an HttpOnly same-site cookie, rejects foreign origins and oversized requests, and installs no background service during npm installation.

The operator scheduler stores one explicit authority and one active claim per loop. Cross-process locks, atomic state, stale-claim recovery, durable cron/wake timestamps, a latest-only missed-run policy, and append-only actor/surface/spec-hash audit events keep control attributable. All run actions delegate to @loopyc/runtime; artifacts remain independently runnable and removable.

LoopSpec artifacts allowlists are indexed with symlink, traversal, MIME, secret, file-count, and byte ceilings. LoopSpec notify names logical generic-webhook channels whose URL/token come only from LOOPY_NOTIFY_<CHANNEL>_URL and optional _TOKEN environment variables. Delivery uses stable idempotency keys, bounded metadata-only payloads, transient retries, deduplication, failure-streak suppression, and audit events; observer failures never alter the run result.

Guarded evolution stores complete candidate YAML outside the artifact, derives only bounded journal summaries, and runs deterministic validation, verification, scoring, regression, capability, and recipe-fixture gates. Fatal gates cannot be waived; safety expansions require every exact gate ID in an attributable approval. Activation and rollback refuse live runs, conditionally update the registry hash, preserve journal history, and restore the prior source byte-for-byte. See the guarded-evolution contract.