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

@felixfelicis/waxwing

v0.1.0

Published

Inspectable architecture diagrams for humans and coding agents.

Readme

Waxwing

Inspectable architecture diagrams for humans and coding agents.

Turn a structured system model into interactive diagrams with linked documentation, source evidence, and explicit unknowns. Export portable HTML and SVG with the model included.

Explore the live demo · Agent guide · Examples · Contributing

Waxwing showing its own architecture

Waxwing is an early, personally maintained project. The formats are experimental; validation checks structure and consistency, not whether your evidence is true. Software version 0.1.0 is the first release; model formats retain their own draft versions.

Try it

Requires Node.js 20.19.0 or newer. No server or account is needed to view the exported diagrams.

npm install -g @felixfelicis/[email protected]

Copy the full command above. The package name includes its publisher namespace; once installed, the terminal command is simply waxwing.

Build the included example:

waxwing build-site "$(npm root -g)/@felixfelicis/waxwing/examples/waxwing/model.json" ./waxwing-demo --direction DOWN

Open waxwing-demo/index.html in your browser. The command above uses macOS/Linux shell syntax; on Windows, run npm root -g and use its printed path in place of $(npm root -g). This real example models a pinned revision of Waxwing itself:

  1. Open Waxwing: from model to artifact and select Layout engine to inspect its claims.
  2. Follow Inside architecture layout to see the coordinator, validators, and ELK boundary.
  3. Open A successful architecture build for the explicit call order, then Read this example for the explanation and source links.

The graph describes dependencies; the workflow describes a scoped successful execution path. Both retain the underlying component identities and evidence.

Use it with your coding agent

Give your agent AGENT_GUIDE.md, access to the code you want to understand, and a concrete question:

Use the Waxwing agent guide to explain how this repository handles an incoming request. Inspect the code, create a partial architecture model with evidence linked to the source revision, and preserve unknowns. Validate the model and build an HTML diagram in a separate output directory.

The installed guide is at $(npm root -g)/@felixfelicis/waxwing/AGENT_GUIDE.md on macOS/Linux. Use the guide from your installed version. It contains complete authoring examples and commands. You choose the agent; Waxwing's layout and rendering do not call an LLM. There is no built-in repository crawler or ingest command.

Build the model your agent produces:

waxwing build /path/to/model.json /path/to/output

Open output/diagram.html. It contains the diagram, its inspector, registered Markdown documents, and the source model. Share that HTML file as an attachment, or use build-site to generate linked pages for static hosting.

What you can inspect

  • Architecture and subgraphs: move between an overview and selected internals.
  • Workflows and sequences: follow explicit ordering, replies, loops, and alternatives.
  • Evidence and uncertainty: inspect why a claim exists and what remains unknown or disputed.
  • Linked Markdown: navigate between explanations and specific diagram records.
  • Recoverable source: extract the complete embedded model from supported exports.
waxwing recover /path/to/diagram.html /path/to/recovered-model.json

Recovery preserves the parsed source model; it does not authenticate the original claims or certify that an exported drawing has not been altered.

Documentation and development

From a source checkout:

git clone https://github.com/pavelnedved/waxwing.git
cd waxwing
npm ci
npm test
npm run test:package

test:package installs a packed archive in a temporary directory and exercises its CLI, module imports, and source recovery. It needs npm registry access.

No visual editing, automatic factual repair, or live infrastructure discovery is implemented. Difficult layouts can fail validation; see the current boundaries.

MIT licensed. Third-party notices.