Our great sponsors
-
container-shell
Starts and attaches a sandboxed shell using docker with access to the current or project directory
-
BrowserBox
🌀 Browse the web from a browser you run on a server, rather than on your local device. Lightweight virtual browser. For security, privacy and more! By https://github.com/dosyago
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Check out https://github.com/jrz/container-shell it is one of the use cases. Not a VM but a docker container
This sucks. Supply chain is such an issue.
Even tho we don't currently target any npm releases, I make use of socket.dev to monitor my project by creating an npm release for it. But my project BrowserBox (lightweight virtualized web browser) only uses ~800 dependencies including all descendents, with only 19 top-level deps (cool your heels non-JavaScript folks, this is comparatively lightweight for a full stack boing).
I'm considering just snapshotting all 800 deps into a @browserbox namespace at npm. And then tracking any vulnerabilities discovered and patching the fixes.
It sounds crazy, but that's where we are. At least that way I "own" all the dependencies and can guarantee (up to company security at least) that we don't have supply chain vulns on the Node/JS side.
https://socket.dev
https://github.com/BrowserBox/BrowserBox
Are you using an Nvidia GPU?
https://github.com/QubesOS/qubes-issues/issues/5104
https://github.com/QubesOS/qubes-issues/issues/7591
If not, try this: https://github.com/QubesOS/qubes-issues/issues/6880#issuecom...
There is no tearing on my Librem laptops.