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

nanosandbox

v0.3.3

Published

Lightweight cross-platform sandbox for secure code execution

Readme

nanosandbox (Node.js)

Node.js bindings for nanosandbox, built with napi-rs.

npm install nanosandbox
const { Sandbox, MB } = require("nanosandbox");

const sandbox = Sandbox.builder()
    .workingDir("/tmp")
    .memoryLimit(128 * MB)
    .build();

const result = sandbox.run("echo", ["hello"]);
console.log(result.stdout);

run() blocks the JS thread until the command ends, so timers, I/O and any other requests your process is serving stall meanwhile. In a server or an agent loop, use the Promise versions, which run on libuv's thread pool and leave the event loop free:

const result = await sandbox.runAsync("echo", ["hello"]);
const piped = await sandbox.runWithInputAsync("cat", [], Buffer.from("hi"));

The thread pool has 4 threads by default (UV_THREADPOOL_SIZE), so more concurrent runs than that queue behind each other.

On macOS, /tmp and the other system temp directories are the host's own and writable. .sharedTmp(false) makes them read-only, leaving only the run's private $TMPDIR; it breaks programs that write /tmp by name, mktemp -t and Apple's /usr/bin/clang/cc shims (see docs/platform-macos.md). macOS only.

See the main README for the full API.

Building from source

Only needed if you're changing the binding itself -- end users want npm install nanosandbox above, which installs a prebuilt binary.

npm install
npm run build
npm test