rsyscall
quickjs-emscripten
rsyscall | quickjs-emscripten | |
---|---|---|
6 | 21 | |
66 | 1,130 | |
- | - | |
3.9 | 9.4 | |
almost 2 years ago | 20 days ago | |
Python | TypeScript | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rsyscall
- Reforming Unix
- A Conceptual Introduction to Rsyscall
-
Ask HN: Who Wants to Collaborate?
Can you say what left you confused?
I'm surprised, I thought https://github.com/catern/rsyscall is pretty self-contained and self-explanatory (if unclear on what exactly rsyscall is useful for), and I thought http://catern.com/integration.html is quite detailed (perhaps excessively so).
- Preventing Log4j with Capabilities
-
Running code within another process's address space
That's one of the things I use this kind of primitive for in https://github.com/catern/rsyscall
quickjs-emscripten
-
New QuickJS Release
Based on your comment below I think you figured out the difference - but if you're looking to execute JS, you can pick between ShadowRealm (where available, or using a polyfill) or my library quickjs-emscripten.
Pros of quickjs-emscripten over ShadowRealm:
- You can use quickjs today in any browser with WASM. ShadowRealm isn't available yet, and polyfills have had security issues in the past. See https://www.figma.com/blog/an-update-on-plugin-security/
- In ShadowRealm eval, untrusted code can consume arbitrary CPU cycles. With QuickJS, you can control the CPU time used during an `eval` using an [interrupt handler] that's called periodically during the eval.
- In ShadowRealm eval, untrusted code can allocate arbitrary amounts of memory. With QuickJS, you can control both the [stack size] and the [heap size] available inside the runtime.
- quickjs-emscripten can do interesting things with custom module loaders and facades that allow synchronous code inside the runtime to call async code on the host.
Pros of ShadowRealm over QuickJS:
- ShadowRealm will (presumably?) execute code using your native runtime, probably v8, JavaScriptCore, or SpiderMonkey. Quickjs is orders of magnitude slower than JIT'd javascript performance of v8 etc. It's also slower than v8/JSC's interpreters, although not by a huge amount. See [benchmarks] from 2019.
- You can easily call and pass values to ShadowRealm imported functions. Talking to quickjs-emscripten guest code requires a lot of fiddly and manual object building.
- Overall the quickjs(-emscripten) API is verbose, and requires manual memory management of references to values inside the quickjs runtime.
[interrupt handler]: https://github.com/justjake/quickjs-emscripten/blob/main/doc...
[stack size]: https://github.com/justjake/quickjs-emscripten/blob/main/doc...
[heap size]: https://github.com/justjake/quickjs-emscripten/blob/main/doc...
[benchmarks]: https://bellard.org/quickjs/bench.html
-
Extism Makes WebAssembly Easy
The thing I want to achieve with WebAssembly is still proving a lot harder than I had anticipated.
I want to be able to take strings of untrusted code provided by users and execute them in a safe sandbox.
I have all sorts of things I want this for - think custom templates for a web application, custom workflow automation scripts (Zapier-style), running transformations against JSON data.
When you're dealing with untrusted code you need a really robust sandbox. WebAssembly really should be that sandbox.
I'd like to support Python, JavaScript and maybe other languages too. I want to take a user-provided string of code in one of those languages and execute that in a sandbox with a strict limit on both memory usage and time taken (so I can't be crashed by a "while True" loop). If memory or time limit are exceeded, I want to get an exception which I can catch and return an error message to the user.
I've been exploring options for this for quite a while now. The furthest I've got was running Pyodide inside of Deno: https://til.simonwillison.net/deno/pyodide-sandbox
Surprisingly I've not found a good pattern for running a JavaScript interpreter in a WASM sandbox yet. https://github.com/justjake/quickjs-emscripten looks promising but I've not found the right recipe to call it from server-side Python or Deno yet.
Can Extism help with this? I'm confident I'm not the only person who's looking for a solution here!
-
Node on Web. Use Nodejs freely in your browser with Linux infrastructure.
"Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions" quickjs-emscripten, NPM
-
Sandboxing JavaScript Code
This maybe, as a start?
https://github.com/justjake/quickjs-emscripten
-
Hacker News top posts: Nov 20, 2022
QuickJS Running in WebAssembly\ (17 comments)
-
QuickJS Running in WebAssembly
The library was inspired by Figma’s blog posts about their plug-in system: https://github.com/justjake/quickjs-emscripten#background
-
Show HN: Run unsafe user generated JavaScript in the browser
If you need to call into user-generated Javascript synchronously or have greater control over the sandbox environment, you can use WebAssembly to run a Javascript interpreter: https://github.com/justjake/quickjs-emscripten#quickjs-emscr...
QuickJS in WebAssembly is much slower than your browser's native Javascript runtime, but possibly faster than async calls using postMessage. As an added bonus, it can make async functions in the host appear to be synchronous inside the sandbox using asyncify: https://emscripten.org/docs/porting/asyncify.html.
-
Why Would Anyone Need JavaScript Generator Functions?
You can use One Weird Trick with generator functions to make your code "generic" over synchronicity. I use this technique to avoid needing to implement both sync and async versions of some functions in my quickjs-emscripten library.
The great part about this technique as a library author is that unlike choosing to use a Promise return type, this technique is invisible in my public API. I can write a function like `export function coolAlgorithm(getData: (request: I) => O | Promise): R | Promise`, and we get automatic performance improvement if the user's function happens to return synchronously, without mystery generator stuff showing up in the function signature.
Helper to make a function that can be either sync or async: https://github.com/justjake/quickjs-emscripten/blob/ff211447...
Uses: https://cs.github.com/justjake/quickjs-emscripten?q=yield*+l...
-
Why Am I Excited About WebAssembly?
This seems like a pretty nice, recently enabled way of getting a sandboxed js environment: QuickJS compiled to WASM: https://github.com/justjake/quickjs-emscripten.
What are some alternatives?
go-littr - Link aggregator inspired by (old)reddit using ActivityPub federation. (mirror repository) [Moved to: https://github.com/mariusor/brutalinks]
wasmtime - A fast and secure runtime for WebAssembly
bangle-io - A web only WYSIWYG note taking app that saves notes locally in markdown format.
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
DK86PC - A WIP Intel 8086 and IBM PC 5150 emulator.
wizer - The WebAssembly Pre-Initializer
camera-preview - Capacitor plugin that allows camera interaction from HTML code
rr - Record and Replay Framework
linux-insides - A little bit about a linux kernel
go - The Go programming language
macrome - The in-tree build system
iPlug2 - C++ Audio Plug-in Framework for desktop, mobile and web