供应链安全与模块验证
通过签名、验证和来源追踪实践，保护 WASM 部署免受篡改和恶意依赖的影响。
供应链安全与模块验证 是 CoddyKit 上的免费 WebAssembly (WASM) for High Performance Apps 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 WebAssembly (WASM) for High Performance Apps 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 WebAssembly (WASM) for High Performance Apps 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Beyond the Sandbox
The WASM sandbox protects the host at runtime, but it does not guarantee the module you run is the one you trust. Supply chain security covers where the bytes came from.
Threats to Address
Key risks:
- Tampered modules in transit or storage
- Compromised build pipelines
- Malicious third-party WASM dependencies
Integrity with Hashing
Pin a module by its content hash so any byte change is detected before instantiation.
import crypto from "node:crypto";
import fs from "node:fs";
const bytes = fs.readFileSync("app.wasm");
const hash = crypto.createHash("sha256").update(bytes).digest("hex");
if (hash !== EXPECTED) throw new Error("integrity check failed");Signing Modules
Cryptographic signatures prove authorship. The publisher signs the module; the host verifies with the corresponding public key before running it.
Verifying Before Instantiate
Always verify integrity/signature before calling WebAssembly.instantiate — never run untrusted bytes and check afterward.
Provenance & Attestation
Build attestations (e.g. SLSA) record how and where a module was built, letting you reject artifacts not produced by your trusted pipeline.
Auditing Dependencies
A WASM module may bundle third-party code. Track a bill of materials (SBOM) and scan dependencies for known vulnerabilities.
Reproducible Builds
Deterministic builds let independent parties rebuild the same module and confirm the hash matches, defeating hidden tampering in the toolchain.
Registry Security
When pulling modules from a registry, use signed references and pin versions/digests rather than mutable tags to prevent substitution attacks.
Runtime Allowlisting
Maintain an allowlist of approved module hashes in production. The host refuses to instantiate anything not on the list.
Defense in Depth
Combine sandbox + signing + provenance + capability limits. No single layer is sufficient; together they shrink the attack surface dramatically.
Quick Check
When should signature verification happen?
Recap
Supply chain security complements the runtime sandbox: use hashing for integrity, signatures for authorship, provenance/SBOM for trust, verify before instantiation, and allowlist approved hashes in production.
常见问题解答
「供应链安全与模块验证」课时是免费的吗？
是的 — 「供应链安全与模块验证」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 WebAssembly (WASM) for High Performance Apps 课程的其余内容，请升级到 CoddyKit PRO。 WebAssembly (WASM) for High Performance Apps 课程共包含 4 节课。
「供应链安全与模块验证」这节课中我会学到什么？
通过签名、验证和来源追踪实践，保护 WASM 部署免受篡改和恶意依赖的影响。 你通过在浏览器中直接运行的动手代码来练习 WebAssembly (WASM) for High Performance Apps，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 WebAssembly (WASM) for High Performance Apps 需要有经验吗？
无需任何先前经验。CoddyKit 上的 WebAssembly (WASM) for High Performance Apps 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「供应链安全与模块验证」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 WebAssembly (WASM) for High Performance Apps 课中编写并运行代码吗？
能。每节 WebAssembly (WASM) for High Performance Apps 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。