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

@mayurajs/sandbox-codesandbox

v1.2.0

Published

CodeSandbox (Together) sandboxes for mayura/sandbox, through the CodeSandbox SDK.

Readme

@mayurajs/sandbox-codesandbox

CodeSandbox (Together) sandboxes for mayura/sandbox: Firecracker microVMs forked from a template, through the CodeSandbox SDK (@codesandbox/sdk).

npm install mayura @mayurajs/sandbox-codesandbox @codesandbox/sdk
import { createSandboxes } from 'mayura/sandbox';
import { codeSandboxSandboxes } from '@mayurajs/sandbox-codesandbox';

const sandboxes = createSandboxes(codeSandboxSandboxes({ apiKey }), {
  maxSandboxes: 5, maxLifetimeMs: 3_600_000,
  network: ['all'], // CodeSandbox VMs always reach the internet
});
const sandbox = await sandboxes.create({ lifetimeMs: 600_000, network: 'all' });
const result = await sandbox.exec(['node', '-e', 'console.log(6 * 7)']);
await sandbox.release();
  • CodeSandbox VMs reach the internet, and this provider has no way to stop them, so it cannot enforce the network 'none': sandboxes are created only with 'all', listed in createSandboxes and asked for.
  • Sandboxes are created private (CodeSandbox's own default is public), forked from template (its universal template by default; a sandbox's image names another), on vmTier (your workspace's default otherwise). cpus and memoryMiB are refused, and labels become tags (at most 10).
  • CodeSandbox has no maximum lifetime: a release deletes the sandbox at its lifetime, and it hibernates when idle for that long (at most a day) should the release never come. A hibernated sandbox is kept, and can cost storage, until you delete it.
  • CodeSandbox runs commands in a terminal, which joins and changes their output, so commands write their output to files, of which only as much as is kept is read back; standard input travels as a file. A timeout or cancellation kills the command's shell and every process carrying its tag. Files use the SDK's file system.
  • url(port) gives a URL with a host token that lasts as long as the sandbox; anyone with it can open the port.
  • The SDK is a peer you install yourself (@codesandbox/sdk 2.4.2 or a later 2.x): it brings its command line's dependencies with it, some of which declare no licence (such as buffers), so Mayura does not install it for you. It is loaded when first needed and typed here by its shape, since its own type files do not resolve under NodeNext. With sdk you pass a client you made instead. Node only. Options: apiKey (or sdk), template, vmTier, workdir (/project/sandbox), maxLifetimeMs (24 hours).

See the sandbox guide. Apache-2.0.