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

@pactmark/testing

v0.2.0

Published

Deterministic Pactmark fakes and reusable adapter contract suites

Readme

@pactmark/testing

Deterministic test infrastructure and reusable adapter conformance suites for Pactmark.

The package exports a controllable clock and ID generator, scripted model and tool fakes, boundary crash injection, a scenario builder, and framework-independent store, tool executor, and egress contract runners. It is intended only for tests and development dependencies; it must not be imported by Pactmark production package exports.

Contract runners throw ContractViolation at the first violated invariant and otherwise return an immutable report naming every passed check. They do not depend on Vitest or another test framework, so adapters can invoke them from their own test runner.

runStoreContracts runs the accepted-work-order, input-submission, event, context, artifact, and lease suites. The lease factory is a harness because the contract must advance adapter time without consulting host time. Individual runners remain available when an adapter implements only one port.

The adapter conformance runners are:

  • runToolExecutorContract for exact registration dispatch, runtime JSON/schema validation, pre-dispatch abort, and capability/error-surface claims.
  • runEgressBrokerContract for tenant-bound declared egress, cancellation, and zero transport on denied requests. runEnforcedEgressContract remains the separate real-isolation probe suite.
  • runRunCommandUnitOfWorkContract for full-scope replay, changed-request-digest rejection, cross-tenant command-record binding, and the advertised atomic command/wakeup capability.
  • runMCPUntrustedToolAdapterContract for MCP-style protocol boundaries: exposed digest routing, malformed input/output rejection, cross-tenant and unexposed-tool denial, abort, and safe public errors. Its structural harness keeps protocol SDKs out of this package.

Each runner accepts a factory so every scenario starts from caller-owned adapter state and uses caller-owned counters or observations. Error checks operate on the public serialization returned by the harness's errorSurface function; secrets used to exercise an upstream failure must not appear in that JSON-safe surface, and the surface must contain a stable KAF_* code.

@pactmark/testing belongs in an adapter's devDependencies only. Production packages must not import or re-export these runners. Concrete integrations should live in package-local adapter tests for executor, egress, durable store, and MCP adapters respectively.

The fakes do not model provider or network behavior beyond their explicit scripts. In particular, passing an egress contract only proves the behavior exercised by the supplied probe harness; an adapter may advertise enforced network isolation only when the harness maps every required probe to a real isolation boundary.