HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wasmerio
wasmer
Rust2018–2026
wasmerio / wasmer

wasmer

🚀 Fast and lightweight sandboxes for your apps and AI agents

34Distinct people
56Mentions
0Explicit recommenders
21.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🚀 Fast and lightweight sandboxes for your apps and AI agents

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 10:50:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year56 dated mentions

Observed mentions: 2018-12-08 03:04:12 UTC to 2026-01-29 03:41:46 UTC.

0369122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC12210
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC606
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1019
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC10010
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC918
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Lightweight sandboxes for your apps and AI agents Run with the CLI ¡ Embed with the SDK ¡ Try in your browser Wasmer runs your apps in fast, secure, and lightweight sandboxes: locally, in the cloud, or in your browser. Secure by default. You control file, network, and environment access. Lightweight. Fast startup with a small memory footprint. Ready to run. Python, JavaScript, Bash, and more from the registry. Embeddable. Add sandboxes to your app with the Wasmer SDK. Run your first sandbox Install the CLI on macOS or Linux: curl https://get.wasmer.io -sSfL | sh Windows and other installation options Windows (PowerShell) iwr https://win.wasmer.io -useb | iex Homebrew (macOS / Linux) brew install wasmer See the installation guide for more options. Run Python in a sandbox: wasmer run python/python -- -c "print('Hello from Wasmer')" Hello from Wasmer Or try a shell command and Cowsay: wasmer run wasmer/bash -- -c "echo 'Hello from Wasmer'" wasmer run syrusakbary/cowsay -- "Hello from Wasmer" Wasmer downloads the package and caches it for future runs. Use -- to separate Wasmer options from the arguments passed to your program. To work with local files, grant access to a directory with --volume; enable host networking with --net when your program needs it. See the CLI guide for details. No installation needed: open wasmer.sh to try a sandbox in your browser. Wasmer SDK Create a sandbox, choose your tools, and run code directly in your app with the Wasmer SDK. Install the SDK JavaScript / TypeScript (Node.js 20 or newer): npm install @wasmer/sdk Rust The Rust SDK currently uses a source dependency. Clone wasmerio/wasmer-sdk, then point your application at its rust directory: [dependencies] wasmer-sdk = { path = "../wasmer-sdk/rust" } tokio = { version = "1", features = ["macros", "rt-multi-thread"] } Follow the Rust setup guide for the required toolchain and workspace patches. Crates.io publishing is currently disabled. Python python -m pip install wasmer-sdk The SDK's Python wheels support macOS and Linux on Intel and ARM64. See the Python guide. Swift (iOS and macOS) Use Swift 6 or newer. The SDK supports macOS 12+ and iOS 27+; iOS apps require Xcode 27 or newer. Add the package to your Package.swift dependencies: .package( url: "https://github.com/wasmerio/wasmer-sdk.git", revision: "wasmer-sdk-swift-v0.4.0" ) Then add the product to your target's dependencies: .product(name: "WasmerSDK", package: "wasmer-sdk") In Xcode, you can instead add the repository URL, select wasmer-sdk-swift-v0.4.0 as a revision, and choose the WasmerSDK product. SwiftPM downloads the prebuilt macOS binaries and iOS runtime resources. For iOS, set the deployment target to iOS 27.0 and allow local networking in your app's Info.plist: <key>NSAppTransportSecurity</key> <dict> <key>NSAllowsLocalNetworking</key> <true/> </dict> Both platforms use import WasmerSDK and the same API. On iOS, the SDK manages a hidden WKWebView; your app does not need to display one. See the Swift guide and iOS setup guide for more details. Run code in a sandbox JavaScript / TypeScript Save this as sandbox.mjs: import { Wasmer } from "@wasmer/sdk/node"; const wasmer = new Wasmer(); const sandbox = await wasmer.sandboxes.create({ packages: ["python/python@=3.13.20"], }); const output = await sandbox .command("python", ["-c", "print('Hello from Wasmer')"]) .run(); console.log(output.text()); Run it with node sandbox.mjs. Python executes inside the sandbox; you don't need Python installed on the host. See the JavaScript guide. Python example Save this as sandbox.py: import asyncio from wasmer_sdk import Wasmer async def main(): wasmer = Wasmer() sandbox = await wasmer.sandboxes.create( packages=["python/python@=3.13.20"], ) output = await sandbox.command( "python", ["-c", "print('Hello from Wasmer')"] ).run() print(output.text()) asyncio.run(main()) Run it with python sandbox.py. See the Python guide. Swift example (iOS and macOS) Use this code in an async throws context: import WasmerSDK let wasmer = try Wasmer() let sandbox = try await wasmer.sandboxes.create( packages: ["python/python@=3.13.20"] ) let output = try await sandbox.command( "python", ["-c", "print('Hello from Swift!')"] ).run(timeout: 30) print(try output.text()) See the Swift guide for embedding in an iOS or macOS app and more examples. JavaScript in the browser Use the same JavaScript sandbox API with the @wasmer/sdk/browser import. Execution happens in the browser. Your page needs cross-origin isolation (Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp) for worker-backed execution. Follow the browser setup guide or explore wasmer.sh. Rust example use wasmer_sdk::{Result, Wasmer}; #[tokio::main] async fn main() -> Result<()> { let wasmer = Wasmer::new()?; let sandbox = wasmer .sandboxes() .create() .package("python/python@=3.13.20") .await?; let output = sandbox .command("python") .args(["-c", "print('Hello from Wasmer')"]) .run() .await?; println!("{}", output.text()?); Ok(()) } See the Rust guide for workspace setup and more examples. Go further Build more with the sandbox API: Commands. Run code and capture output. Processes. Stream output and manage long-running tasks. Files. Read and write the sandbox workspace. Tools. Combine languages and packages in one sandbox. Services. Run servers with explicit network access. The SDK is currently alpha. See the language guides for platform support and capabilities, and the SDK examples for Python scripts, an Edge.js HTTP server, PostgreSQL, and multiple tools sharing one sandbox. Software you can run Start with packages from the registry: Software Package Python python/python JavaScript / Node.js-compatible app
Read the full README on GitHub

What Hacker News says

10 sources
I'm not entirely convinced Wasmer will ever be able to shake its constant controversies. I'm by no means a fan of the Bytecode Alliance, and would much prefer a startup tackle the problems that Wasmer is tackling, but between the trademarks [1], the lackluster response to the trademarks (How did you not know your lawyers were trying to trademark “WebAssembly”? Seriously?) [2], the working conditions [3], the drama surrounding the BCA [4][5], and everything else, I don't think Wasmer is the right choice either, at least not under current leadership. [1] https://uspto.report/company/Wasmer-Inc [2] https://wasmer.io/posts/wasmer-and-trademarks [3] https://mnt.io/2021/10/04/i-leave-wasmer/ [4] https://github.com/wasmerio/wasmer/issues/956 [5] https://github.com/WebAssembly/WASI/issues/3
In Wasmer takes WebAssembly libraries mainstream with WAI
Java had an extremely advanced and strict sandbox for many years. It offered of course also the possibility to blacklist everything by default. The problem with such a granular sandbox is that it's too complex for most use cases. When you need to whitelist any and every call to the outside world this becomes very tedious. That's why Java now removes the sandbox… https://inside.java/2021/04/23/security-and-sandboxing-post-... Let's see how this works out for WASM. I guess: Without resorting to using some language(s) with build-in support for capability security a whitelist based sandbox approach won't ever work without issues. First of all you can forget about C/C++. Everything in this languages assumes free access to the system. Rust does not have any support for capabilities either (yet, and for the years to come at least). The best curr
Read the rest
ent WASM sandbox implementation, which is in WasmTime not Wasmer, is not more than a FS block. (And the memory safety guaranties you get in any VM language, of course). https://docs.wasmtime.dev/security.html I don't find any such feature mentioned in the Wasmer docs. It seems completely without any sandbox! (To stress it once more: All VM languages are memory safe. That's not sandboxing. All the "sandboxed by default" claims are misleading, at least). https://github.com/wasmerio/wasmer/issues/221 That even people here on HN believe in the currently unfulfilled WASM security promises shows only how good the WASM marketing is. This should make you even more skeptical. One should never over promise on security! Java had to learn this the hard way over many years (as their sandbox had have holes in the past, and was also almost impossible to correctly configure).
In Wasmer 3.0
Hey Conlectus, let me address your technical comments (note: I work at Wasmer) > 1. Lack of support for `externref`, AKA opaque references to host data. We do support `externrefs`, but had to partially disable it due to big impacts on performance due to how we did the initial implementation. We are refactoring this in Wasmer 3.0 and this shall be completely addressed in the Wasmer 3.0 release. > 2. An awkward context API for host calls. This is probably the point I agree most with. This is already being worked on. Please take a look on this PR if you are interested on knowing how things will look like for Wasmer 3.0 [1] > 3. It took me about 2 weeks of development to run into a use-after-free bug bubbling up into Rust. Sorry to hear that! We are working hard make sure there are no such leaks/bugs in Wasmer > 4. The performance, at least f
Read the rest
or my use case, was not meaningfully better than Wasmtime In general, being able to have to have a pluggable compiler infrastructure I think makes the runtime infrastructure way more resilient and with almost zero effort we should be able to support more chipsets (such as RISC-V). In the case of Wasmtime they are using the partially-optimized compiler Cranelift, but they only support for x86_64 and aarch64. They are doing super interesting things such as the ISLE initiative but IMHO they are far from having the robustness that projects like LLVM already have. Which is why Wasmer chose a pluggable compiler infrastructure rather than tying itself to only one. > 5. Lack of support for instance resource allocation pools. Yup, this is on our plans! > 6. Lack of support for the module linking proposal This have been very intentional. IMHO module linking is an over-engineered solution that can be solved more easily with a static spec definition outside of Wasm. I personally think it's unlikely that it will reach broad adoption. But I can assure you that Wasmer will implement this once browsers do (if they ever do, of course) [1]: https://github.com/wasmerio/wasmer/pull/2892
In Wasmer – Universal WebAssembly Runtime
You can import host functions and data to a WASM VM much like you would with, say, an embedded Python VM. The exact API depends on which VM implementation and host language you're using. dlopen/dlsym support is still in the works (for example, see [0]). You can't call function pointers directly from WASM, naturally, but it is possible to wrap dlsym so you can use it from a WASM program. There just isn't a standardized/pre-made way to do it yet, so you'd have to write the glue code yourself. [edit] The Emscripten WASM toolchain seems to support dlopen/dlsym, see: https://github.com/WebAssembly/tool-conventions/blob/main/Dy... [0] https://github.com/wasmerio/wasmer/issues/1995
In WebAssembly 2.0 First Working Draft

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.