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

@notmike101/iframe-sandbox-runtime

v0.1.0

Published

Browser-only iframe sandbox runtime for executing untrusted UI code in an isolated frame with controlled DOM access.

Readme

@notmike101/iframe-sandbox-runtime

Browser-only iframe sandbox runtime for executing untrusted UI code in an isolated frame while exposing a controlled DOM surface to the sandboxed code.

Installation

From npm:

npm install @notmike101/iframe-sandbox-runtime

From GitHub Packages:

npm install @notmike101/iframe-sandbox-runtime --registry=https://npm.pkg.github.com

Usage

import SandboxRuntime from "@notmike101/iframe-sandbox-runtime";

const sandbox = new SandboxRuntime(
  "preview",
  `
    document.body.innerHTML = "<h2>Sandbox output</h2>";
    console.log("sandbox ready");
  `,
);

sandbox.run(document.querySelector("#preview-root"));

API

new SandboxRuntime(name, code, overrideExisting = false)

Creates a named sandbox instance for the provided source string.

  • name: unique string key for the sandbox instance
  • code: JavaScript source to execute inside the isolated iframe
  • overrideExisting: replace an existing sandbox with the same name when true

sandbox.run(target = document.body, allowAccessToTarget = true)

Appends the hidden iframe to target and starts execution.

  • target: host element the sandbox can interact with
  • allowAccessToTarget: when false, sandbox execution loses direct same-origin access to the host target

sandbox.destroy()

Stops managing the iframe, removes it from the DOM, and unregisters the sandbox name.

SandboxRuntime.getSandbox(name) / getSandbox(name)

Returns a previously created instance by name.

Constraints

  • Browser-only package. It requires document, iframe, and crypto.randomUUID().
  • The sandbox intentionally exposes parts of the host DOM when allowAccessToTarget is true.
  • This is not a hardened security boundary for hostile third-party code; it is a constrained browser runtime helper.

Development

npm install
npm run dev
npm run check

The demo page is served by Vite and exercises the source package directly during development.