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

@flowwright/control-plane

v0.1.1

Published

Framework-independent FlowWright control-plane service layer.

Readme

@flowwright/control-plane

@flowwright/control-plane contains the framework-independent domain services behind the FlowWright team application. The NestJS server adapts these services to HTTP, while the standalone worker reuses the same execution and queue logic directly.

FlowWright · Server · Worker

What it owns

| Area | Responsibilities | |---|---| | Projects and runs | Project lifecycle, checkout, plan loading, triggering, comparison, and replay | | Execution plane | Durable queue, scheduling, worker pools, leases, recovery, cancellation, and retention | | Security | Authentication providers, sessions, RBAC services, password hashing, secrets, and policy | | Integrations | Signed webhooks, run ingestion, JUnit parsing, logs, artifacts, and archives | | Operations | Health, metrics, rate limiting, backup, configuration, reconciliation, and structured logging | | Read models | Runs, projects, workers, audit, queue, storage, search, and dashboard views |

Composition

The package exports functions and service contracts rather than a framework module:

import {
  createWorkerPool,
  createTokenAuthProvider,
  createRateLimiter,
  runProject,
} from "@flowwright/control-plane";

Deployable hosts construct stores, loggers, executors, and configuration, then pass them into these services. This makes the same behavior usable from NestJS controllers, workers, integration tests, and future host frameworks.

Design boundary

HTTP host ──adapt──▶ control-plane services ──compose──▶ core + runtime
  • No module imports @nestjs/*; transport concerns stay in apps/server.
  • API shapes come from @flowwright/api-contract.
  • Pipeline and policy contracts come from @flowwright/core.
  • Execution and repositories come from @flowwright/runtime.
  • Browser UI and CLI concerns do not belong in this package.

This package is primarily an internal application layer. Use the flowwright-server unless you are building a custom host or extending FlowWright itself.

Development

$ pnpm --filter @flowwright/control-plane typecheck
$ pnpm --filter @flowwright/control-plane test
$ pnpm --filter @flowwright/control-plane build

Tests cover services, scheduling, worker protocol, configuration as code, secrets, reconnection, logging, metrics, and log access.

Requires Node.js 24+. Licensed under MIT.