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

@airalogy/airalogy-engine

v0.0.1

Published

Airalogy protocol execute sandbox

Downloads

75

Readme

airalogy-engine (Node.js)

Airalogy protocol execution sandbox for Node.js/TypeScript. Run protocol packages (parse, assign, validate) inside a secure BoxLite sandbox.

Installation

pnpm add @airalogy/airalogy-engine

Sandbox Image

The engine runs protocol code in a BoxLite sandbox. You can use either a remote Docker image or a local OCI rootfs directory.

Remote Image

const result = await parseProtocol(protocolPath, undefined, {
  image: "numbcoder/airalogy-engine:0.1",
});

Local OCI Rootfs (Recommended)

Build and export the image locally for faster, offline execution:

docker build -t airalogy-engine:latest .
docker save airalogy-engine:latest -o airalogy-engine-image.tar
mkdir airalogy-engine-image
tar -xf airalogy-engine-image.tar -C airalogy-engine-image

Then use rootfsPath:

const result = await parseProtocol(protocolPath, undefined, {
  rootfsPath: "./airalogy-engine-image",
});

If neither image nor rootfsPath is provided, the engine falls back to the default remote image numbcoder/airalogy-engine:0.1.

Usage

import { parseProtocol, assignVariable, validateVariables } from "@airalogy/airalogy-engine";

const protocolPath = "/path/to/your/protocol";
const options = { rootfsPath: "/path/to/airalogy-engine-image" }; // or { image: "..." }

// 1. Parse the protocol
const parseResult = await parseProtocol(protocolPath, { API_KEY: "xxx" }, options);
console.log(parseResult.data?.meta_data);
console.log(parseResult.data?.json_schema);

// 2. Assign a variable
const assignResult = await assignVariable(
  protocolPath,
  "duration",
  { seconds: 3600 },
  { API_KEY: "xxx" },
  options,
);
console.log(assignResult.data);

// 3. Validate variables
const validateResult = await validateVariables(
  protocolPath,
  { seconds: 60, duration: "PT1M" },
  { API_KEY: "xxx" },
  options,
);
console.log(validateResult.data);

API

parseProtocol(protocolPath, envVars?, options?)

Parse a protocol and return its schema, metadata, and fields.

assignVariable(protocolPath, varName, dependentData, envVars?, options?)

Assign a variable value using the protocol's assigner functions.

validateVariables(protocolPath, vars, envVars?, options?)

Validate variable values against the protocol's model.

All functions return Promise<ProtocolResult>:

interface ProtocolResult {
  success: boolean;
  message?: string;
  data?: Record<string, unknown>;
  output?: string;
}

Sandbox Options

All functions accept a SandboxOptions object:

| Option | Type | Default | Description | |---|---|---|---| | image | string | "numbcoder/airalogy-engine:0.1" | Remote Docker image name | | rootfsPath | string | — | Path to a local OCI rootfs directory (overrides image) | | timeout | number | 300 | Execution timeout in seconds. The sandboxed process will be killed once it times out| | memoryMib | number | 512 | Memory limit in MiB | | cpus | number | 1 | CPU limit | | debug | boolean | false | Enable executor debug logging inside the sandbox | | logFile | string | "protocol_debug.log" | Host file to append sandbox debug logs to |

Development

cd node

# Install dependencies
pnpm install

# Build (copies executor + compiles TypeScript)
pnpm run build

# Type check
pnpm run type-check

# Lint
pnpm run lint

# Run tests
pnpm test

Testing

Tests use vitest and support both sandbox modes via environment variables:

# Default: remote Docker image mode
pnpm test

# Use local OCI rootfs
SANDBOX_MODE=rootfs ROOTFS_PATH=../airalogy-engine-0.1 pnpm test

# Custom remote image
SANDBOX_IMAGE=numbcoder/airalogy-engine:0.1 pnpm test