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

orrery-diagrams

v0.4.0

Published

Animated, navigable architecture diagrams from a JSON model: validate, render, export and embed. The orrery command.

Readme

orrery-diagrams

Animated, navigable architecture diagrams from a JSON model, built for AI agents to author. This is the orrery command; the model and the renderer are @orrery-diagrams/core, the layout engine @orrery-diagrams/layout-elk, the in-file engine @orrery-diagrams/runtime. The whole story, with pictures, is in the repository README.

npm install -g orrery-diagrams        # or: npx orrery-diagrams …
orrery validate app.orrery.json                       # OK: 6 components, 7 connections, ... or one pointer-addressed error per line
orrery render app.orrery.json -o app.svg              # one SVG: animated in an <img>, interactive when opened directly
orrery render app.orrery.json --static -o app.svg     # one view, no runtime
orrery render app.orrery.json --view checkout-seq -o seq.svg   # a sequence view, a file of its own
orrery render app.orrery.json --scenario db-fails --step 1     # a still of that moment
orrery export app.orrery.json --out docs/             # every picture the model's `exports` lists
orrery embed app.orrery.json --out site/              # the diagram, the engine and a sample page for your own page
orrery packs aws                                      # every kind a vocabulary pack defines
orrery --help                                         # every option

Layout is automatic; the file never contains coordinates. Every property of the model is described in the JSON Schema (@orrery-diagrams/core/schema/v1.json) and specified in docs/MODEL.md. The providers' icon packs are separate packages under the providers' terms: npm install @orrery-diagrams/pack-aws, then "kinds": { "use": ["aws"] }.

Node 22 or newer. MIT.