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

msdbox

v0.1.9

Published

A tiny UMD execution utility with a pure-JS interpreter (for environments that disallow eval/new Function).

Readme

msdbox

A lightweight JavaScript interpreter that executes UMD bundles and JavaScript code in secure sandboxed environments, perfect for environments with Content Security Policy (CSP) restrictions that disallow eval and new Function().

npm version npm downloads

Features

  • 🚫 No eval/Function: Pure JavaScript interpreter implementation
  • 🔒 Safe execution: Sandboxed environment with timeout support
  • 📦 UMD support: Execute UMD bundles and retrieve exports
  • Lightweight: Minimal dependencies, tree-shakable exports
  • 🔧 Flexible: Advanced interpreter API for custom use cases

Playground

Try msdbox online

The playground includes interactive demos for:

  • Self-interpreter execution
  • Timeout protection
  • Sandbox isolation
  • Running popular libraries (jQuery, React, Vue, ECharts, Angular.js, Knockout)

Install

npm i msdbox

Quick Start

Basic Usage

import { executeUmd } from 'msdbox'

const { exported, costMs } = executeUmd<{ hello: string }>(
  'module.exports = { hello: "world" }',
  { timeoutMs: 1000 },
)

console.log(exported.hello, costMs) // "world", <execution-time>

API Reference

executeUmd<T>(code, options?)

Execute UMD script code and return the exported value.

Parameters:

  • code (string) — UMD script source text
  • options (object, optional)
    • timeoutMs (number, default: 8000) — Execution timeout in milliseconds
    • globalVarName (string, optional) — Fallback global variable name (used only if module.exports is empty; reads from this[globalVarName])

Returns:

  • exported (T) — The exported value from module.exports or the fallback global variable
  • costMs (number) — Execution time recorded by the interpreter (milliseconds)

Example:

const result = executeUmd(
  `
    var x = 1 + 2;
    module.exports = { sum: x };
  `,
  { timeoutMs: 5000 }
)

console.log(result.exported.sum) // 3
console.log(result.costMs) // <execution-time>

Advanced Usage

Interpreter API

For lower-level control (e.g., run non-UMD snippets, reuse a single context, or implement custom bootstrap logic), use the underlying interpreter exports.

Exports:

import { Interpreter, evaluate, vm, InterpreterFunction } from 'msdbox'
  • Interpreter — The interpreter class (runs code against a provided sandbox/context)
  • evaluate — Convenience wrapper to run code in a context
  • vm — Node-like helpers (runInContext, compileFunction, etc.)
  • InterpreterFunction — Interpreter-backed Function constructor (safer alias to avoid confusion with global Function)

Minimal Example

import { Interpreter } from 'msdbox'

const sandbox: Record<string, any> = { console }
const interpreter = new Interpreter(sandbox, { timeout: 1000 })

const result = interpreter.evaluate('var x = 1 + 2; x')
console.log(result) // 3

Custom Context Example

import { Interpreter } from 'msdbox'

const customContext = {
  Math,
  console,
  customVar: 42,
}

const interpreter = new Interpreter(customContext, {
  timeout: 5000,
  ecmaVersion: 5,
})

const result = interpreter.evaluate(`
  var doubled = customVar * 2;
  Math.max(doubled, 10);
`)
console.log(result) // 84

Build

npm run build

Build outputs are written to dist/ and exposed via package.json#exports (both ESM and CJS entrypoints, tree-shakable).

Development

Local Testing

npm pack
npm link

Project Structure

  • src/execute.ts — UMD execution utilities
  • src/internal/vendor/interpreter/ — Pure JavaScript interpreter implementation
  • dist/ — Compiled output (generated)

License

MIT