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

@msn-control/liftoff

v0.2.1

Published

Mission Control Liftoff CLI for scaffolding enterprise GenAI applications.

Readme

Liftoff CLI

Status: implemented.

Liftoff is the Mission Control Launchpad Engine package under tools/liftoff-cli. It exposes the liftoff command and scaffolds enterprise GenAI applications with FastAPI, PydanticAI, Docker Compose, OpenTofu, and spec-driven governance assets.

Installation

Install the latest stable CLI globally:

npm install -g @msn-control/liftoff@latest

After installation, run:

liftoff help
liftoff create

Contract conventions

Generated projects contain persistent files that outlive any CLI release. The following rules are the compatibility contract, enforced by tests/contract.test.ts where possible:

  • Manifest schema: liftoff.manifest.json uses artifactVersion 2 — the first supported schema version — recording the generating CLI version (liftoffVersion) and a sha256:-prefixed contentHash per artifact. Readers accept every supported version and reject others with a remedy; writers always write the latest version.
  • Append-only identifiers: artifact logicalNames and catalog ids (patterns, providers, environments, spec workflows) are never renamed or removed, only added. The contract test snapshots the logical-name sets.
  • Deterministic rendering: artifact content depends only on the project plan and the template code — no timestamps, randomness, or environment leakage. Verified by a double-render byte-equality test.
  • Reserved namespaces: .liftoff/ in generated projects is reserved for future CLI-managed state; no new CLI-managed root-level files beyond liftoff.config.json and liftoff.manifest.json. liftoff.config.json is written once at generation and never machine-written afterwards.
  • Portable paths: machine-readable files store OS-neutral path-part arrays, never joined path strings.
  • Exit codes: 0 = success or clean check, 1 = failure, 2 = a check mode found drift.
  • Machine output: every --json output carries a top-level numeric schemaVersion.

Development

Repository-local commands are for contributors working from a Mission Control checkout. Run package commands from the repository root:

npm run build
npm test
npm run check

Or run them directly in this workspace package:

npm run check --workspace @msn-control/liftoff

Run the package smoke test before publishing:

npm run smoke:package --workspace @msn-control/liftoff

Release

The Release Liftoff workflow builds, tests, packs, smoke-installs, and publishes only the @msn-control/liftoff workspace package. Stable versions publish with the latest npm dist-tag; prerelease versions publish with next.

Prefer npm trusted publishing with provenance for release authentication. If trusted publishing is not configured for the repository and npm organization, create a scoped npm automation token and store it as the repository secret NPM_TOKEN.