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

@axiom-lattice/microsandbox-service

v0.0.9

Published

`@axiom-lattice/microsandbox-service` runs an HTTP service for managing microsandbox-backed sandbox lifecycle operations.

Downloads

839

Readme

@axiom-lattice/microsandbox-service

@axiom-lattice/microsandbox-service runs an HTTP service for managing microsandbox-backed sandbox lifecycle operations.

This package is intended to be deployed as a long-running process. Its primary runtime entrypoint is the lattice-microsandbox-service CLI.

Install and Build

Build the package from the monorepo root:

pnpm --filter @axiom-lattice/microsandbox-service build

After building, you can start the service through the package CLI or the package start script.

CLI Usage

The package exposes this executable:

lattice-microsandbox-service

Supported flags:

  • --host <string>
  • --port <number>

Example:

lattice-microsandbox-service --host 0.0.0.0 --port 4002

Configuration

Runtime configuration is resolved in this order:

  1. CLI arguments
  2. Environment variables
  3. Defaults

Supported environment variables:

  • HOST default: 0.0.0.0
  • PORT default: 4002

Example:

HOST=0.0.0.0 PORT=4002 lattice-microsandbox-service

Startup Examples

Start with CLI flags:

lattice-microsandbox-service --host 127.0.0.1 --port 4002

Start with environment variables:

HOST=127.0.0.1 PORT=4002 lattice-microsandbox-service

Start through the package script:

pnpm --filter @axiom-lattice/microsandbox-service start

Check service health:

curl http://127.0.0.1:4002/health

Process Manager Examples

systemd

[Unit]
Description=Axiom Lattice Microsandbox Service
After=network.target

[Service]
ExecStart=/usr/local/bin/lattice-microsandbox-service --host 0.0.0.0 --port 4002
Restart=on-failure
Environment=HOST=0.0.0.0
Environment=PORT=4002

[Install]
WantedBy=multi-user.target

supervisor

[program:microsandbox-service]
command=/usr/local/bin/lattice-microsandbox-service --host 0.0.0.0 --port 4002
autostart=true
autorestart=true
environment=HOST="0.0.0.0",PORT="4002"

docker

CMD ["lattice-microsandbox-service", "--host", "0.0.0.0", "--port", "4002"]

Local Development

Run the package in watch mode from the monorepo root:

pnpm --filter @axiom-lattice/microsandbox-service dev

This command watches source files, rebuilds the package, and restarts the service automatically.

Operational Notes

  • Invalid startup configuration exits non-zero.
  • Startup failures exit non-zero.
  • SIGINT and SIGTERM trigger graceful shutdown.