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

create-hlao-deployment

v0.1.1

Published

Scaffold generator for HLAO deployment kits. Run once per org (or client) to produce a clean deployment repo depending on @hlao/* engine packages, wired to the three-layer HLAO model (engine + adapters + deployment kit).

Vulnerabilities

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

Links

Git

Maintainers

eleviagroupeleviagroup

Keywords

Readme

create-hlao-deployment

Scaffold generator for HLAO deployment kits. One command produces a clean skeleton ready for an organization to fill in the seven org-specific things (identity, routing, credentials, workflows, agents, verifyActor, deploy shape) and start running.

Usage

npx create-hlao-deployment my-org-name

That produces a directory my-org-name/ containing:

  • config/identity.md — blank template for who the org is (voice, rules, authority scopes)
  • config/routing.md — blank template for which workflow handles what
  • workspaces/_template/ — copied from the engine; numbered stages, CONTEXT.md files, .review-gate markers ready to be duplicated per workflow
  • src/ — TypeScript bootstrap wired to @hlao/* from npm
    • engine.ts — composes @hlao/authority, @hlao/passport, @hlao/mcp-gateway, @hlao/orchestrator, @hlao/audit, @hlao/memory, @hlao/audit-query
    • verifyActor.ts — stub with instructions on installing one of the @hlao-adapter/google-sso-* packages (or writing your own)
    • workflow.ts — stage-runner scaffold
    • index.ts — entry point
  • docker-compose.yml — local-first deploy shape per ADR-0013
  • .env.example — every credential slot documented and empty
  • .gitignore, tsconfig.json, package.json — the usual
  • README.md — walks the org through the seven things in order

The generated repo already depends on the correct @hlao/* versions from npm public. No workspace links, no clone-the-engine-first step. The adopter runs pnpm install and they're ready to fill in.

The three-layer HLAO model this fits into

Deployment Kit  (this generator produces one of these)
    depends on
Adapters        (@hlao-mcp/* for data sources, @hlao-adapter/* for identity)
    depends on
Engine          (@hlao/* — the workflow-agnostic substrate)

The generator ships nothing org-specific. Everything a specific organization needs to fill in is either a blank template (identity, routing) or a stub with clear replace-me instructions (verifyActor, workflows, credentials).

What this generator does NOT do

  • Pick your identity provider. The verifyActor stub tells you which adapter to install (@hlao-adapter/google-sso-oidc, @hlao-adapter/google-sso-oauth, or @hlao-adapter/google-sso-directory) based on your app shape; you install and wire.
  • Pick your MCP servers. The .env.example lists every @hlao-mcp/* package with a comment naming the credentials each needs. You install only the ones your org uses.
  • Define your workflows. workspaces/_template/ is a shape, not a workflow. You copy it, rename it, and fill in the stages.
  • Choose an agent runtime. Per ADR-0017 LangGraph is recommended, but the engine is silent on runtime. The generator's workflow scaffold works with any runtime that meets the engine's contract.

Development

git clone https://github.com/joelbyler272/create-hlao-deployment.git
cd create-hlao-deployment
pnpm install
pnpm build
pnpm test

# Test the generator locally against a scratch dir:
node dist/cli.js /tmp/scratch-org