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

@orkestrel/study

v0.0.15

Published

Runs declared comparative studies with admitted requests, sealed execution custody, and independent grading. Part of the @orkestrel line.

Readme

@orkestrel/study

Bounded comparative execution with captured artifacts and separate grading.

Study schedules declared populations, admits requests before dispatch, retains execution bytes, and grades sealed results independently. Consumer adapters supply domain behavior.

Install

Install Study in your consumer workspace.

npm install --save-dev @orkestrel/study

Study requires Node.js 22.18.0 or later. TypeScript consumers of the server entry must also install @types/node because its declarations import node: modules. The core entry needs no Node.js types.

For the server declarations, add the type prerequisite.

npm install --save-dev @types/node

Package entries

Import the entry for your execution environment. Each entry supports ESM import and CommonJS require.

Within one module format, the root and server entries share one StudyError class, so both instanceof StudyError and isStudyError recognize server errors. The ESM and CommonJS builds carry separate classes. Across module formats, recognize a server error with isStudyError; instanceof StudyError is false.

| Export | Import | Provides | | ---------- | ------------------------- | ----------------------------------------------------------------------------------------- | | . | @orkestrel/study | Host-independent engine, contracts, guards, and parsers | | ./server | @orkestrel/study/server | Custody, native workers, command classes, Agent instrumentation, and the Ollama transport |

Run the study executable

The package installs the study executable. From your consumer workspace, invoke the local command through npm.

npm exec -- study --help
npm exec -- study --version

The study --help command prints the command reference. The study --version command prints the installed Study version. Use the operations for validation, execution, independent grading, label import, and reporting.

| Operation | Command | | ----------------------- | ------------------------------------------------------------------------------- | | Validate declarations | study check <study> [--profile <name>] | | Execute a study | study execute <study> [--profile <name>] [--out <path>] [--expected <sha256>] | | Grade retained evidence | study grade <result> --rubric <path> | | Import semantic labels | study label <result> --assessment <sha256> --labels <path> | | Report an exact grading | study report <result> --assessment <sha256> |

Declare a study at studies/<name>/study.json. Its rubric path resolves inside that study directory. Its driver field selects a bundle at studies/<driver>/ containing the adapter module index.ts, scenario declarations at scenarios/<scenario>.json, and execution profiles at profiles/<profile>.json. The profile defaults to local.

Results default to tmp/studies/<result>. A result selector can be an identity under that directory, a root-relative path, or an absolute path. Relative paths must stay inside the consumer workspace. Output directories must be absent before execution.

Read the exit code to distinguish outcomes.

| Exit code | Meaning | | --------- | --------------------------------------------------- | | 0 | Success | | 64 | Invalid input, including a missing declaration file | | 124 | Deadline | | 130 | Interruption | | 1 | Operational failure, including a missing result |

Documentation

For the contracts, declaration layout, and executable behavior, see the Study guide. For the guide map, see the guide index.

Development

Run the package checks and read-only guide proof.

npm test
npm run test:guides