node-seccomp
Low level libseccomp bindings for Node.js (by roryrjb)
proposal-shadowrealm
ECMAScript Proposal, specs, and reference implementation for Realms (by tc39)
Our great sponsors
node-seccomp | proposal-shadowrealm | |
---|---|---|
1 | 19 | |
3 | 1,376 | |
- | 2.5% | |
0.0 | 6.0 | |
over 2 years ago | 11 days ago | |
C++ | HTML | |
MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
node-seccomp
Posts with mentions or reviews of node-seccomp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-11.
-
Node.js packages don't deserve your trust
I was exploring the actual implementation[0] of a capabilities feature in Nodejs and was utilising seccomp (via libseccomp) on Linux at least to achieve a greater degree of security than might otherwise be possible by remaining in userland code. The idea is that you'd write your code, import whatever you like and define your capabilities upfront at initialisation. The problem is there's quite a big disconnect between what you are doing in JavaScript and what's happening with system calls in v8, libuv and the other native parts that it's difficult to predict what you need to block and what's actually going to happen. So I don't think my approach is really viable in a general sense, although capabilities in general I think would improve the situation if the wider community were to adopt the approach.
[0]. https://github.com/roryrjb/node-seccomp
proposal-shadowrealm
Posts with mentions or reviews of proposal-shadowrealm.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-29.
-
Updates from the 98th TC39 meeting
ShadowRealm: ECMAScript Proposal, specs, and reference implementation for Realms [Stage 3 -> 2].
-
Should you use jest as a testing library?
You can't out of the box. There is an open issue on the Node.js repositoryto let the node:vm module to use the vm's context, but it is still open. It seems that the Node.js core team is interested in fixing this problem by implementing the new ShadowRealm spec, and I think we will make some progress during 2023.
-
Building an Extension System on the Web
ShadowRealms — a successor of the Realms proposals, this API is intended for use cases exactly like plugins or extension systems, providing an option for creating distinct global environments to run the code in. While not entirely secure on its own, this API could provide a strong foundation to build actual extension systems on the Web. That said, 4 years later, the TC39 proposal is currently only at stage 3, not implemented by any browser;
-
Vitest vs Jest benchmarks on a 5 year old real work SPA
With --no-isolate it was 2.8x faster than vitest and 1.7x faster than Jest, but 19 tests failed (see table above). Some people report issues with watch mode when using --no-isolate. So I decided to not pursue it any further. Once the vm module that Vitest relies on supports ESM, or when the amazingly named Shadow Realms are added to JavaScript, we will likely get this performance boost for free without the downsides.
-
Improving Vitest Performance
If ShadowRealms are ever added to EcmaScript (and implemented into V8/Node) they'll allow for a different approach to isolating code that would be faster without the downsides of sharing global.
- Virtualization is not an important enough use case for the web platform to tradeoff ergonomics and possible confusion for web devs, who by and large […] do not understand the separation between the specs. More to the point, they really shouldn't need to.
-
Is there an npm package for perchance?
Eventually I will get around to creating a "proper" package by just grabbing all the JS that is loaded by the code in the iframe, and bundling it up. We really need the ShadowRealm proposal to go through because the perchance engine messes with a lot of JS internals, so it would mess up the rest of your app. Could do it in a WebWorker, but then everything would have to be async.
-
Show HN: Run unsafe user generated JavaScript in the browser
The upcoming JavaScript Shadow Realms proposal looks like it solves a similar problem: https://github.com/tc39/proposal-shadowrealm/blob/main/expla...
- Named Element IDs Can Be Referenced as JavaScript Globals
-
Running user code in the browser (for a leetcode clone)
Browser-based JavaScript doesn't yet have a way to isolate code fully in this manner though there is a new JavaScript feature on the way that would provide this capability. Its called ShadowRealm and would basically give you a new global context to execute code that's completely separate from your main document code.
What are some alternatives?
When comparing node-seccomp and proposal-shadowrealm you can also consider the following projects:
ansi-italic - The color italic, in ansi.
wtfjs - 🤪 A list of funny and tricky JavaScript examples
proposal-ses - Draft proposal for SES (Secure EcmaScript)
Pentive - Collaborative Spaced Repetition
rua - Build tool for Arch Linux providing control, review and jailed build options
vm2-process - Execute unsafe javascript code in a sandbox
vrite - Open-source developer content platform
caja - Caja is a tool for safely embedding third party HTML, CSS and JavaScript in your website.
LavaMoat - tools for sandboxing your dependency graph
proposal-symbol-thenable
EventSource - a polyfill for http://www.w3.org/TR/eventsource/
node-seccomp vs ansi-italic
proposal-shadowrealm vs wtfjs
node-seccomp vs proposal-ses
proposal-shadowrealm vs Pentive
node-seccomp vs rua
proposal-shadowrealm vs vm2-process
proposal-shadowrealm vs vrite
proposal-shadowrealm vs caja
proposal-shadowrealm vs LavaMoat
proposal-shadowrealm vs rua
proposal-shadowrealm vs proposal-symbol-thenable
proposal-shadowrealm vs EventSource