Package Transparency for WebAssembly Registries
summary
Warg is a concrete protocol that makes a Wasm package registry auditable by publishing per-package append-only signed logs and a global verifiable map (Merkle + sparse radix trees) whose paired root checkpoints are signed by the registry. Clients verify only relevant package leaves; long-running monitors process all checkpoints to detect mississued updates, hidden yanks, or key rotations. Reference implementation is in Rust with HTTP APIs and protobufs and is intended to compile to Wasm for wide deployment.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:49Why WebAssembly matters
- 4:53Need for secure registries
- 6:37Certificate transparency for registries
- 8:25Warg implementation
- 15:23Verifiable logs and maps
- 19:55Mitigating attacks
- 21:19Summary
- 22:03Q&A
- 26:13Registry use cases
- 27:40Key compromise recovery
- 31:31Extending Warg
- 32:15Implementation details
related talks
09mLightning Talk: SIG-Registries and Standardizing Package Management in...
43mRichWasm: Bringing Safe, Fine-Grained, Shared Memory Interoperability to WebAssem...
46mWebAssembly (Digging a bit deeper)
49mWasmer Things: An Upside-Down Guide to WebAssembly
21mRichWasm: Bringing Safe, Fine-Grained, Shared-Memory Interoperability Down to WebAssembly
01h 08mOn WebAssembly
26mWebAssembly for a Reactive Internet of Things
36mwRPC: Distributed Components, No Assembly Required
