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

@mozartec/mos-cli

v0.3.1

Published

The mos CLI: serve any vault's board and wiki locally (`mos serve`), scaffold a new vault (`mos init`), and validate one (`mos validate`). Read-only over existing vaults; ships the built web app bundled with the vault endpoints in one Node process.

Readme

@mozartec/mos-cli

mos (markdown on steroids) renders a folder of markdown as a wiki and a Kanban board. The folder is the source of truth; the app is strictly read-only — your editor and your AI agent do the writing.

Requires Node ≥ 20.

Quick start

npx @mozartec/mos-cli init    # turn the current folder into a vault
npx @mozartec/mos-cli serve   # board + wiki at http://127.0.0.1:4400

Or install globally for a plain mos command:

npm i -g @mozartec/mos-cli
mos init && mos serve

Commands

| Command | What it does | | --- | --- | | mos serve [dir] [--port <n>] | Serve the vault at dir (default: the nearest vault at or above the current directory). Live-reloads on file changes. | | mos init [dir] | Scaffold a vault: starter .mos/config.json, one example card, an AGENTS.md write guide. One-time bootstrap — refuses to touch an existing vault. | | mos validate [dir] | Validate the vault(s) at or under dir (default: the current directory) against .mos/config.json. Exits non-zero if any vault has errors — usable as a CI check. | | mos --version / mos --help | Version / usage. |

What a vault is

Any folder containing .mos/config.json. Markdown files under board/ whose frontmatter declares a configured type are cards on the board; the rest of the folder renders as a wiki. Card types, states, and columns all come from the config — nothing about your vocabulary is hardcoded. Internal links (id references like T-001 and ordinary relative markdown links) navigate in-app, and the same files render unchanged on GitHub.

The full format contract, the architecture, and the agent-driven write convention live in the mos repository — start with docs/12-ADOPTING.md.

Read-only by design

mos serve has no write endpoint and rejects non-GET requests; init never overwrites a file. Every change to your vault happens through your editor or your AI assistant.

License

MIT