Not exactly, the chromium/chrome sandbox isn’t dependent on how and what code you execute the electron/node one is and that is because the latter were designed to execute code across many more privilege levels than what “dedicated” browser needs.

If I download and build chromium (as long as I don’t disable the sandbox altogether) I don’t actually need to think about those issues while I do need to do that with Electron.

Is Chromium’s sandbox insecure?

Electron has local file access, etc. in fact, it states: “Under no circumstances should you load and execute remote code with Node.js integration enabled.”

So, Stealth should consider forking Electron if better sandboxing is needed.

https://www.electronjs.org/docs/tutorial/security

That doesn’t prevent it from being secure, though.