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

@sovea/stetra

v0.0.1-alpha.1

Published

CLI for the Stetra engineering harness for coding agents.

Readme

@sovea/stetra

CLI for carrying a coding change from developer intent through Runtime-collected facts to an inspectable handoff.

npm install --global @sovea/stetra
cd /path/to/project
stetra init .
stetra doctor . --strict

init generates a thin Codex and/or Claude Code workflow. The normal agent path uses three JSON commands:

stetra change prepare . --input - --json
stetra change collect . --run <run-id> --json
stetra change finalize . --run <run-id> --json
  • prepare compiles the task contract and proportional Assurance Plan, captures the dirty/untracked worktree baseline, and freezes explicit checks.
  • collect executes those checks without a shell and records the complete actual change, patch, ordered check attempts, output integrity, and verifier-surface mutations. Runtime supplies the normal timeout budget; an actually timed-out check can retry in the same run with --retry-check <id>=<larger-milliseconds>.
  • finalize rejects stale facts and binds the agent's claims, unknowns, falsification, and Review Map to the current collection.

Finalize returns a structured handoffPacket containing the compact Semantic Contract, collected Runtime facts, Agent-authored handoff, and Core evaluation. The generated Host renders it in the current conversation language while keeping paths, IDs, statuses, commands, numeric facts, quoted evidence, and logs exact. No locale or rendered prose is persisted by Runtime.

The Assurance Plan is explicit and inspectable. Routine work can omit claims and Review Map entries when no semantic or factual escalation applies. Standard and critical work must cover declared material or adoption-critical dimensions, while failed checks, verifier mutations, unrepresentable changes, unknowns, and Host-disclosed critical claims can only add obligations.

Exact canonical detail is available on demand:

stetra change explain . --run <run-id> --section contract --json
stetra change explain . --run <run-id> --section facts --json
stetra change explain . --run <run-id> --section handoff --json
stetra change explain . --run <run-id> --section evaluation --json
stetra change explain . --run <run-id> --section review --json

The CLI owns project initialization, task-run IO, exact repository-evidence windows, Git and check collection, bounded logs with complete-stream digests, fact-staleness detection, retention, and deterministic review-packet assembly. The host agent cannot submit changed-file or check facts; it owns user-facing handoff prose.

handoff-ready means ready for developer review, never adopted. needs-attention and rejected results identify exact references and the next repair, evidence, validation, recollection, or direct-review action. The Host explains their adoption impact to the developer.

The CLI pins the exact matching @sovea/stetra-core version. Neither package calls an LLM.