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

aldina

v0.1.0

Published

An open-source engine that turns content and a theme into on-brand, print-grade documents. Built on ChoirMark.

Readme

Aldina

An open-source engine for producing documents — letters, reports, and decks — that come out on-brand and print-grade. You bring content and a theme; Aldina lays out the page. Built on ChoirMark, an open document format.

How it works

Aldina takes a resolved ChoirMark document (roles assigned) and runs a fixed pipeline:

ChoirMark → compose (into a theme grammar) → gate (admit / reject) → project (PDF)

Layout is deterministic wherever it can be, with bounded LLM checkpoints (role inference, deck routing, repair) reserved for the steps that genuinely need judgment. The gate is the heart of it: it admits only pages that pass hard checks — fit, contrast, hierarchy — so a page that doesn't measure up is rejected rather than shipped.

See PIPELINE.md for the two flows (make-the-grammar vs. make-the-document) and the ChoirMark spec for the source format.

Usage

node src/aldina.js <source.cmk> --class letter --theme oxford --out forme.html --pdf out.pdf

Requires a headless Chromium on the PATH (or set CHROMIUM) for the gate and PDF projection.

Themes

Base themes live in themes/ (e.g. oxford). A theme is tokens + a per-class grammar that targets ChoirMark roles ([data-role]) — Zen Garden at the role layer. A new role or class is a ChoirMark spec change, never a theme feature; that's what keeps the interface stable.

License

Dual-licensed: AGPL-3.0-or-later for the engine and base themes, with a commercial license available for uses the AGPL doesn't fit. See LICENSING.md; contributions are governed by CLA.md.

aldina.io · choirmark.org