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 🙏

© 2024 – Pkg Stats / Ryan Hefner

secure-vm

v1.0.6

Published

Experimental JavaScript sandbox based on iframe for frontend (electron, micro apps, etc).

Downloads

6

Readme

⭐ secure-vm

🧪 Experimental vm() based on iframe for frontend (electron, micro apps, etc).

CodeFactor Visitors 🛠️ Build

🇺🇸 | 🇨🇳

❓ What can it do?

👻 It can...

  • [x] 🔐 Run untrusted JavaScript code in an isolated environment.
  • [x] 👽 Pass external APIs (Objects, Functions, Classes) and let untrusted JavaScript code to use them.
  • [ ] ⏱️ Timeout and memory usage limits. See halting problem.
  • [x] ⚛️ Available in electron render. See issue from electron.
  • [x] 🪟 (Almost) Fully transparent. You can even replace vm() with window (if you don't want protection)!
  • [x] 🤔 Keep traceback & code from hackers / DevTools. DevTools will be unable to inspect your code or use debugger.
  • [ ] 🧑‍💻 ESM support (You can use babel to implement that though).

📃 Getting Started

🔽 Install

🦊 npm, yarn & pnpm, etc.

npm install secure-vm
yarn add secure-vm
pnpm install seucre-vm

👾 IIFE (not recommended)

<script src="https://cdn.jsdelivr.net/npm/secure-vm@latest/dist/index.global.js"></script>
<script>
  const ctx = SecureVM.vm()
</script>

✅ Usage

import { vm } from 'secure-vm'

const ctx = vm() // Create an isolated context.
ctx.console = globalThis.console
ctx.eval(`
console.log("Hello secure-vm")
`)

🐺 Compatibility

☣️ This is an experimental library that may be incompatible with some old browser kernels (for example, Opera). However, it works on latest versions of Chromium, Firefox, Edge and Safari.

💫 Try it out by yourself: (Demo not ready)

🛠️ Features

🔰 Ease to use

✅ To create a simple isolation, you only have to use a simple function, vm.

const ctx = vm()

👽 You can bypass almost everything to your sandbox and it will work properly, for example, Promise. (Some functions like ArrayBuffer may not work properly for unknown reasons)

const ctx = vm({ console })
let callback
ctx.test = new Promise(resolve => {
  callback = resolve
})
ctx.eval(`
test.then(value => {
  console.log(value)
})
`)
callback('Hello World!')

🔒 Security

🥰 Feel free to add anything you want, Function (constructor) is gonna be safe.

secure-vm also fixed almost all security issues on evel, for example, Object.prototype bypass will fail.

ctx.fetch = fetch
ctx.console = console
fetch('some furry pics')
  .then(
    ctx.eval(`
req => {
  console.log(req)
  return req.text()
}
`)
  )
  .then(v => {
    console.log(v)
  })

🤖 Dynamic import() is disabled, so you do not need to worry about import bypass. See issue from evel.

Maybe we can run these code by using babel hacks, but we don't care.

import('data:text/javascript,console.log(window)')
// TypeError: Cannot import module from an inactive browsing context. (Chromium)
// TypeError: error loading dynamically imported module: data:text/javascript,console.log(window) (Firefox)

🤔 Obfuscation

🔏 secure-vm will automatically erase the traceback line info (if available) so hackers cannot access source code, making it harder to deobfuscate.

ctx.eval(`
function throwError() {
  throw new Error('Where is it?')
}
throwError() // throwError() will not be displayed in the DevTools traceback (Edge, Chromium, Firefox).
`)

🎨 Customization

😎 You can customize global objects by:

const ctx = vm({ WebAssembly })
ctx. // type hint: WebAssembly

...or use our default whitelist by:

const ctx = vm()

This project is licensed under the MIT license.

❤️