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

workflow-tester

v0.2.0

Published

Contract-driven tests for n8n workflows: generate the payload variants a trigger can receive and check every expression against them, offline

Readme

workflow-tester

CI npm License: MIT

Find the payloads that break your n8n workflow before someone sends them. When a webhook arrives with a field set to null or an optional object missing, n8n turns the broken expression into undefined and shows no error. workflow-tester runs your workflow's expressions against those payloads and tells you which ones break and where. It runs offline, with no n8n instance.

workflow-tester finding an expression that resolves to undefined, then passing after a one-line fix

Installation

Requires Node.js 24 or newer.

Run it without installing:

npx workflow-tester --help

Add it to a project:

npm install --save-dev workflow-tester

Build from source:

git clone https://github.com/LudwigGerdes/workflow-tester.git
cd workflow-tester
pnpm install && pnpm build

Getting started

Set up a project:

npx workflow-tester init

This creates:

.workflow-tester/
├── README.md
└── tests/
    └── example.test.yaml

Download a sample sign-up workflow and a test file with three cases, then run them:

curl -L --create-dirs -o workflows/signup.json https://raw.githubusercontent.com/LudwigGerdes/workflow-tester/main/docs/demo/signup.json
curl -L -o .workflow-tester/tests/signup.test.yaml https://raw.githubusercontent.com/LudwigGerdes/workflow-tester/main/docs/demo/signup.test.yaml
npx workflow-tester run

Expected output:

workflows/signup.json
  ✗ no profile object, flat name — the ?? gotcha  1 expectation(s) fail
      ✗ node.Normalize.output[0].json.name: expected "Bob", got undefined
      ! "profile" is not produced here  at Normalize → assignments.assignments[1].value
      ! "plan" is not produced here  at Normalize → assignments.assignments[2].value
  ! no email at all  every expectation held
      ! "email" is not produced here  at Normalize → assignments.assignments[0].value
      ! "profile" is not produced here  at Normalize → assignments.assignments[1].value
      ! "plan" is not produced here  at Normalize → assignments.assignments[2].value
      ! "email" is not produced here  at Normalize → assignments.assignments[3].value
  ✓ pro user with nested profile

1 passed, 1 failed, 1 warned in 354ms

The first case fails because the workflow reads $json.body.profile.first_name when there is no profile.

Usage

Write a test by hand, in .workflow-tester/tests/:

workflow: ../../workflows/signup.json
cases:
  - id: flat-name
    when:
      trigger: webhook
      payload:
        email: [email protected]
        name: Bob
    then:
      node.Normalize.output[0].json.name: Bob

Run every test:

workflow-tester run

Generate tests from the payloads GitHub or Stripe can send:

workflow-tester contracts add workflows/issue-triage.json --vendor github --events issues-opened
workflow-tester gen
workflow-tester run --only generated

Turn a run you already made in n8n into a test:

workflow-tester capture workflows/invoice.json --execution execution.json

Report in a format your CI understands:

workflow-tester run --format junit

Documentation

Full documentation is at workflowtools.dev/workflow-tester:

License

MIT © Ludwig Gerdes

Bundled n8n node descriptions and the GitHub and Stripe payload catalogues are covered by THIRD_PARTY_NOTICES.md. Not affiliated with n8n GmbH, GitHub or Stripe.