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

@dynobox/sdk

v0.2.0

Published

Dynobox SDK for authoring scenario configs

Downloads

644

Readme

@dynobox/sdk

TypeScript SDK for authoring Dynobox scenario configs.

This package provides the Milestone 1 authoring contract, helper functions, config module resolver, and canonical IR compiler used by the CLI and local runner scaffold.

Current exports

@dynobox/sdk

Authoring helpers for user config files:

  • defineDyno(config)
  • defineScenario(scenario)
  • http.endpoint()
  • http.called()
  • http.notCalled()
  • tool.called(), tool.notCalled()
  • skill.invoked()
  • artifact.exists(), artifact.contains()
  • transcript.contains()
  • finalMessage.contains()
  • sequence.inOrder()
  • dyno helpers

defineDyno(...) also applies authoring defaults for JavaScript and TypeScript dynos: adjacent fixtures/ directories are attached to scenarios that do not set fixtures, and dynos authored under .agents/skills/<name>/ or .claude/skills/<name>/ get setup commands that copy that skill's SKILL.md into the scenario work directory.

@dynobox/sdk/compiler

Compiler and config-loader utilities used by the CLI and integrations:

  • compile(config)
  • resolveConfigModule(moduleExport)
  • configSchema
  • DynoboxConfigError

@dynobox/sdk/ir

Canonical IR contract used by runners and evaluators:

  • IR schemas and derived IR types

Config contract

  • discovered user config names: *.dyno.{mjs,js,ts,mts,yaml,yml}
  • config module shape: default export for JavaScript/TypeScript, same object shape in YAML
  • authoring import path: @dynobox/sdk
  • assertion objects use type plus assertion-specific fields, matching YAML declarations and SDK helper return values
  • file-oriented tool assertions can match paths with tool.called('read_file', {path: 'package.json'}) or the equivalent {type: tool.called, tool: read_file, path: package.json} object shape