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

@eto-press/engine-eto

v3.20260927.0

Published

The eto engine: the editorial machinery that decides what a story is and how it must be told. Prefilter, judge, cluster, the density gates, selection, the compositor, the verification cage.

Downloads

691

Readme

@eto-press/engine-eto

The flagship doctrine: one story, many mouths.

The eto engine decides what a story is — one event, told by at least two outlets that disagree — and how it must be told: a composited brief with the disagreements named in plain words, every source linked, and an end. Stages 1–9 of the pipeline live here, behind the one joint every engine shares: prefilter, judge, cluster, the density gates, cross-edition dedupe, selection, the below-the-fold nomination, the compositor, and the verification cage that checks the compositor's every quote against the accounts it was given.

It asks a model exactly three typed questions — same event, the nomination, the composite — through the platform's inference boundary, and never sees a prompt. Everything else is deterministic code.

Doctrine

One story, many mouths. The disagreement is the story. Nothing unattributed ships. The model composites; it does not comment. Incomplete beats wrong. The masthead is yours.

A paper declares it with [engine] use = "eto" in eto.toml — or by saying nothing, since it is the default. It needs at least one [[source]] in sources.toml and the two local models (eto models pull).

License: AGPL-3.0-only.