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

@nullplatform/workflow-kit

v0.1.0

Published

Author, validate, test and publish nullplatform workflows locally: CLI + the same E2E test harness the platform's own workflow suites use.

Vulnerabilities

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

Links

Git

Maintainers

geisbruchgeisbruchpablovilaspablovilas

Keywords

nullplatformworkflowsworkflow-enginetesting

Readme

@nullplatform/workflow-kit

Author, validate, test and publish nullplatform workflows locally.

  • npx np-workflow validate <yaml> — parse/normalize/schema + dual graph validation (create-time knowledge AND the hosted runtime's knowledge).
  • npx np-workflow publish <yaml> --alias live / run <id> --inputs '{}'.
  • import { runWorkflowE2E } from '@nullplatform/workflow-kit/test' — the same E2E harness the platform's own suites use (local executor, plugin-level stubs).

Build: node build.mjs (bundles the workspace dist, minified, no sourcemaps; hosted-only modules stubbed; no-disclosure post-pass). Pack: npm run pack:local. See nullplatform/workflows for the executable corpus this package powers.

Releasing

Publishing is tag-driven (.github/workflows/publish-kit.yml), target: PUBLIC npm (registry.npmjs.org, org nullplatform, secret NPM_TOKEN).

  1. PR bumping packages/kit/package.json version → merge to main.
  2. git tag kit-v<version> && git push origin kit-v<version>
  3. The action: version==tag guard → workspace build → kit bundle (the no-disclosure post-pass FAILS the build on any hosted-vendor string) → CLI smoke → npm publish --access public → release gate: clones nullplatform/workflows, installs the JUST-published version from the registry and runs the corpus's full E2E suite + validate against it. A red gate means the published version broke the corpus — publish a patch; npm versions are immutable (never re-tag).

Release checklist (before tagging): corpus tests green against the branch tarball (npm run pack:local + npm i --no-save <tgz> in the corpus), np-workflow skill and corpus docs updated if behavior changed.