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

@vensofts-integration-testkit/scenario-pro

v0.1.4

Published

Relational Scenario SDK Pro: constraint-preserving, graph-aware failure reduction against a real application.

Readme

@vensofts-integration-testkit/scenario-pro

Pro features for the NodeSDK Relational Scenario SDK: shrink a failing dataset to a minimal regression, start from ready-made business scenarios, and share readable reports. Commercial license (see LICENSE).

Works with @vensofts-integration-testkit/scenario-core and @vensofts-integration-testkit/scenario-cli. Node.js 22 or newer.

Pricing

The free packages (authz-core, authz-cli, scenario-core, scenario-postgres, scenario-cli, license-core, test-witness) need no license file. The Pro features need a trial or Pro license file; one license covers every Pro package: authz-pro, scenario-pro and suite.

| Plan | Price | Includes | | --------- | ------------------------------- | --------------------------------------------------------------------------- | | Trial | Free for 14 days | Every Pro feature, to try on your own project. Expires after 14 days. | | Pro | USD 299 / year per organization | Every Pro feature for your whole organization, email support. Renew yearly. |

When a license expires, the Pro features stop with exit code 5 until you renew; the free packages keep working. The command line reminds you during a trial and in the last 14 days of a license.

To start a trial or buy Pro, email [email protected] with your organization's name. You receive an invoice, and after payment a license file.

Features

Failure reduction (scenario.reduction)

Your test fails on a dataset with thousands of rows; reduceFailure finds a small dataset that fails the same way.

  1. It confirms the failure several times, so a flaky test is reported as unstable, not reduced.
  2. It removes groups of related rows, then single rows (ddmin), then simplifies values.
  3. Every candidate is checked against your schema before your test runs, and only candidates with the same failure signature are kept.

You get the reduced dataset, a diff and a full trace. The result is a local minimum under these steps, not a global one.

Recipe packs (scenario.packs)

Ready-made schemas and recipes you can adapt:

  • Orders and refunds: line items with exact totals, discounts, orders with two partial refunds, refunds that never exceed the order total, and refund currency matching the order.
  • Subscriptions and quotas: trial, active, expired and cancelled plans, usage just below, at and just above the quota, and a trial that expires exactly at the test clock. These come from a pairwise covering array: every pair of values from any two dimensions appears in some scenario.

Load one with loadPack('orders', entitlement) or loadPack('subscriptions', entitlement).

HTML report (scenario.reports)

A standalone page with planning explanations, SVG dependency graphs for unsatisfiable recipes, validation, coverage, drift and reduction history. It makes no network requests, and is tested for accessibility (no serious or critical issues) in light and dark mode.

See what you get

HTML report. Here a recipe asks for 3 pricing plans with unique codes but only allows two codes. The report proves it is impossible before any row is written, and shows why as a dependency graph:

Scenario HTML report explaining an unsatisfiable recipe

Use with the CLI

npm install --save-dev @vensofts-integration-testkit/scenario-cli @vensofts-integration-testkit/scenario-core @vensofts-integration-testkit/scenario-pro

npx scenario reduce --fixture failing.json --out reduced.json --license license.json

reduce uses the harness from your scenario.config.mjs: a function that runs your test on a dataset and reports whether it fails. Instead of --license, you can set license: { file: 'license.json' } in the config.

Use as a library

Also install @vensofts-integration-testkit/license-core, which loads and checks the license file.

import { readFileSync } from 'node:fs';
import { entitlementOrThrow } from '@vensofts-integration-testkit/license-core';
import { loadPack, reduceFailure, renderScenarioHtml } from '@vensofts-integration-testkit/scenario-pro';

const entitlement = entitlementOrThrow(readFileSync('license.json', 'utf8'), { product: 'scenario' });
const orders = loadPack('orders', entitlement);

The license file

  • Don't commit it to a public repository. In CI, store it as a secret.
  • It is checked offline: no network call and no machine fingerprint.
  • Without a valid license, a Pro feature stops with exit code 5 and a clear message. It never silently does less.