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

@pleasantmachines/kento-contract

v0.1.0

Published

Tests of `@kento/runtime` and the packages above it (`@kento/authority`, `@kento/navigation`, `@kento/frames`, `@kento/fuzz`) through whole games, where an engine test with a toy game would not show the contract holding for a real consumer (save codecs, i

Readme

@kento/contract: the runtime contract suite

Tests of @kento/runtime and the packages above it (@kento/authority, @kento/navigation, @kento/frames, @kento/fuzz) through whole games, where an engine test with a toy game would not show the contract holding for a real consumer (save codecs, input parsing, manifests, long runs across former tick caps). The engine's own tests (engine/<package>/src/*.test.ts) come first; these add the consumer's view. They import only those packages' public entries and the fixtures below, never a game. fuzz.test.ts fuzzes every fixture through sessionSimulation. The fixtures are exported as @kento/contract/fixtures/<name> for other tests; labs pages import them by path.

Fixtures

fixtures/ holds the small games these tests play. Each is a complete GamePackage with its own tests; the first four have a dev page in labs/pages/ (see labs/README.md), the last two are headless agent games with declared scenarios (an agent export) that the agent CLI validates and recovers in real processes.

| Fixture | What it is | Used by | | --- | --- | --- | | movement.ts | Continuous movement at 20 ms ticks around a wall, render-rate independent | fixed, lifetime, tools/bench-runtime.mjs, page movement | | settlement.ts | World laws (calendar, combustion, vitality, optional rain) and scheduled ignition; law add/remove migration | migration, input, game, page world-laws | | negotiation.ts | Nonspatial dialogue game with its own versioned save codec | game, input, page negotiation | | passage.ts | Opposed doorway traffic with admission cohorts | consumer-limits, tools/bench-traffic-progress.mjs, page passage | | vault.ts (+ vault.agent.ts) | Turn-based exploration and combat on two maps: navigationField for the guard, placementModel for maps, occupancy and disposal; win, loss, terminal rejection, retreat, malformed checkpoints (was games/signal-run) | vault.test.ts, tools/engine/{cli,references}.test.mjs, tools/engine/browser/declarations.test.mjs (the browser bundle) | | relays.ts (+ relays.agent.ts) | Scheduled work and entity lifetime across two maps: delayed activation, transfer with pending work, cancel, cascade removal, task-reference validation (was games/timed-relays) | relays.test.ts, tools/engine/{cli,references}.test.mjs |

They are test fixtures, not reference games: no game loads them, they are not in index.ts and not in the agent catalog. Their pages and tools import them by path. The contract tests that need a bigger game live with it in games/: the RTS tick-cap and obsolete-save checks in games/iron-crossing/limits.test.ts, and frames, surface picking and replication through the framed workshop in games/inhabited-workshop/framed/.