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

baset-vm

v0.14.4

Published

VM package for BaseT project.

Downloads

21

Readme

Known Vulnerabilities

BaseT VM

VM for BaseT project.

DISCLAIMER: it was a fork of vm2 package for internal use in baset with some functionality that is missing in original project.

After major overwrite of this module - it's only responsibility is running code in separate node.js context within same proccess, so host isn't required to serialize/deserialize data from it's children. But unlike original vm2 package it's not designed for running untrusted code - normal code won't affect host's environment in most cases but there are NO PROGRAM RESTRICTIONS to do it, so if you know how this context is built and which parts are actually shared between host and child you are able to affect host from child. Such decision is made, because securing host makes vm much slower, which is ok for running untrusted code, but huge overkill for running tests.

If, for some reason, you're interested in vm2 replacement (as I was). Create an issue in this repo - and I'll do my best to make this package production-ready.