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-ledger

v3.20260927.0

Published

The ledger engine: the lay of the land as of yesterday. A board of figures with their motion, the editor's signed columns, then decked links from the outlets' feeds — the business desk and the sports desk in one engine.

Readme

@eto-press/engine-ledger

The numbers speak; the ledger arranges them.

The lay of the land as of yesterday — the business desk and the sports desk in one engine. Three anatomies, in this order:

  1. The board. Sources with kind = "door" are data doors — JSON or plain-text endpoints, an optional #dot.path naming the value — and side names the board they sit on ("Markets", "Scores"). Every figure prints with its motion since the last edition, measured against what the reader last saw.
  2. The columns. The editor's signed pieces from the section's desk (# headline, by: Name, then the take). A byline always means a human.
  3. The desk. Sources without a kind are writers' and outlets' feeds, and side names the shelf they sit on ("Markets", "Trade talk"). Every new post prints as a row — the title as the link, the outlet, a one-line deck. The outlet's own summary is the deck when it has one; otherwise the desk's, asked of the inference boundary and caged.

Nothing is composited. Which of the three matters is the reader's. Nothing moved, nothing new: NoEdition. When anything prints, every board prints, so the section shows the whole state of the world it watches.

Declare it with engine = "ledger" in a [[section]] of eto.toml. It needs the judge model for the deck question and never the compositor.

License: AGPL-3.0-only.