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

@codeforamerica/blueprint-explorer

v0.1.0

Published

Static documentation generator for Blueprint framework projects — contract reference, state machine diagrams, event catalog, and data dictionaries

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

fritzjoostefritzjoostedevowhippitdevowhippitrobdiciucciorobdiciucciochriscorreachriscorreamryhmlnmryhmlnlkacenjarlkacenjar

Keywords

Readme

@codeforamerica/blueprint-explorer

Static documentation generator for Blueprint framework projects — contract reference, state machine diagrams, event catalog, and data dictionaries

npm version license

Pre-release: This package is at 0.x. Until 1.0.0, minor versions may include breaking changes. Pin your version if stability matters.

Installation

npm install --save-dev @codeforamerica/blueprint-explorer

What It Does

Generates a set of static HTML reference tools from resolved Blueprint contract artifacts. Point it at your resolved specs and TypeScript clients to produce a browsable documentation hub that can be published as a GitHub Pages site or any static host.

| Tool | Description | |------|-------------| | API Reference | Endpoint docs derived from resolved OpenAPI specs — parameters, request/response schemas, status codes, and links to related state machine transitions | | Client Reference | TypeScript SDK reference — types, methods, and usage examples per domain | | State Machine Docs | Full state machine reference — states, transitions, guard conditions, actor restrictions, and event subscriptions per resource | | Event Catalog | Cross-domain event index — every emitted event with its publisher, payload schema, and known subscribers | | Data Dictionaries | Field-level reference derived from writable schemas — field names, types, policy citations, and data classifications | | Sequence Diagrams | Key workflow sequences showing cross-domain interactions | | Context Map | Domain relationship diagram showing cross-domain data dependencies |

Usage

# Build all tools
node build.js \
  --content=./packages/safety-net-explorer \
  --resolved=./resolved \
  --clients=./clients

# Build a single tool
node build.js --only=api-reference --resolved=./resolved --clients=./clients
node build.js --only=state-machine-docs --resolved=./resolved
node build.js --only=event-catalog --resolved=./resolved
node build.js --only=data-dictionaries --resolved=./resolved

Output is written to the --content directory as static HTML files. The API reference, state machine docs, event catalog, and data dictionaries update automatically as contracts change — rebuild after each resolve step.

Changelog

See CHANGELOG.md for release history.

Documentation

See the Safety Net Blueprint documentation for full guides and reference.

License

PolyForm Noncommercial License 1.0.0