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

@archsmith/cli

v0.7.0

Published

ArchSmith CLI — render and validate layered architecture diagrams

Readme

@archsmith/cli

The archsmith command-line tool for ArchSmith — render and validate layered architecture diagrams from a JSON IR.

See the root README for what ArchSmith is and what the IR looks like.

Install

npm install -g @archsmith/cli

Usage

The recommended filename pattern is *.archsmith.json, which allows editors and integrations to recognize ArchSmith documents reliably. The CLI accepts any JSON file path.

archsmith author
archsmith validate <input.archsmith.json> [--json]
archsmith render <input.archsmith.json> -o <out.svg> [--no-embed-fonts] [--pretty]
archsmith registries list
archsmith registries show <sub-layers|colors|icons> [--family standard|accessible]
archsmith schema show
  • author launches a guided, no-hand-written-JSON wizard — creates a valid initial diagram one plain-language question at a time, offering only governed colors/sub-layers, then validates, renders, and saves the .archsmith.json and .svg next to each other. Editing an existing diagram isn't supported yet. Needs a real terminal — a piped/non-interactive invocation fails with one clear line rather than hanging.
  • render validates the IR first and fails the same way validate would (exit 1) if it's invalid; a rendering-time error exits 2.
  • --no-embed-fonts skips embedding the bundled font, producing a smaller file.
  • --pretty indents the output SVG's element lines for readability (default is one element per line, unindented).
  • registries show colors --family standard prints just that color family instead of the whole registry. The planned accessible registry can be inspected, but diagrams cannot select it until its complete palette is designed and tested.
  • schema show prints the raw diagram-schema.json contents — the structural contract an IR document must satisfy, as distinct from the governed vocabulary registries exposes.

License

Apache-2.0