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

@adobe/aio-sandbox-run

v1.1.1

Published

Interactive CLI for working with Adobe I/O Runtime compute sandboxes

Readme

Adobe I/O Runtime Sandbox — Interactive CLI

An interactive CLI for creating and exploring Adobe I/O Runtime compute sandboxes.

[!WARNING] Alpha. The underlying SDK is in active alpha development. The API surface and authentication model may change without notice.

Pre-requisites

Sandboxes must be enabled for your Runtime namespace. Contact Michael Goberling ([email protected]) or Cosmin Stanciu ([email protected]) to request access.

Usage

npx github:adobe/aio-lib-sandbox/run --type cpu:default

Credentials are read from environment variables or prompted interactively on first run:

| Variable | Description | |---|---| | AIO_RUNTIME_APIHOST | Runtime API host (default: https://adobeioruntime.net) | | AIO_RUNTIME_NAMESPACE | Your Runtime namespace | | AIO_RUNTIME_AUTH | Your Runtime API key |

Copy .env.example to .env in your working directory to avoid typing credentials each time.

Flags

| Flag | Short | Description | |---|---|---| | --namespace | -n | Runtime namespace | | --apihost | -H | Runtime API host | | --api-key | -k | Runtime API key | | --type | -t | Sandbox type (e.g. cpu:default, cpu:large) | | --size | -s | Sandbox size | | --egress | -e | Egress rule(s) — repeatable (see below) | | --port | -p | Print a preview URL for this port at startup — repeatable |

Egress rules

Sandboxes are default-deny. Use --egress to allowlist outbound endpoints:

# Single rule
npx github:adobe/aio-lib-sandbox/run --egress "api.github.com:443"

# Multiple rules
npx github:adobe/aio-lib-sandbox/run \
  --egress "httpbin.org:443" \
  --egress "api.github.com:443|GET:/repos/**"

# Allow all outbound traffic
npx github:adobe/aio-lib-sandbox/run --egress allow-all

Format: host:port[:TCP|UDP][|METHOD[,METHOD]:/path/pattern]

Preview URLs

Use --port to print preview URLs for servers running inside the sandbox:

npx github:adobe/aio-lib-sandbox/run --port 3000 --port 5173

REPL commands

Once the sandbox is created, you get an interactive REPL:

| Command | Description | |---|---| | <any shell command> | Run command on the sandbox | | cmd <<< "text" | Send inline text as stdin | | .help | Show help | | exit / quit | Destroy sandbox and exit |

Note: Each command runs in a fresh process. Shell state (working directory, exports) does not persist between commands. Chain commands to work around this: cd mydir && npm install.