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

@tomflow/proflow-module-contract

v0.1.12

Published

Defines the canonical governance contract for ProFlow modules.

Vulnerabilities

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

Links

Maintainers

tomflowtomflow

Keywords

proflowproflow-moduledeployment-governance

Readme

@tomflow/proflow-module-contract

Runtime schemas shared by ProFlow Module packages, Module Template, deployment conformance and Platform CLI.

Standard management contract

Every governed Module adapter exposes exactly seven standard capabilities:

install / uninstall / status / setup / docs / start / stop

Additional Module-specific commands may exist, but they are not part of the Platform standard proxy surface.

Status observation

setupStatus: READY | ACTION_REQUIRED | BLOCKED | FAILED
runtimeStatus: RUNNING | STOPPED | FAILED | NOT_APPLICABLE

The Module owns these facts. Platform validates and aggregates the shape only; it does not derive readiness or invent an unknown runtime state.

Operation result

Module operation results use SUCCEEDED, ACTION_REQUIRED or FAILED. ACTION_REQUIRED is reserved for real human or external participation and includes an executable action description. Machine-owned failures return FAILED with a typed error.

BLOCKED is a Platform orchestration/aggregation outcome, not a Module operation result status.

Configuration boundary

Public ConfigSlot entries describe only values that genuinely require user or external-world input. Deterministic Workspace paths, fixed loopback values, Module-owned artifact paths, secret material and facts provided by another Module must not be turned into user configuration.

Dependency and documentation boundary

provides/requires describe runtime topology, Contract discovery and ordering; package managers own package dependency resolution and mutation. Cross-Module data travels through Producer-owned public Contracts/shared facts rather than Platform-owned configuration.

DOCS.md and SETUP.md are the standard Module-owned knowledge files. The adapter docs and setup capabilities expose the current knowledge and executable setup guidance.