✦ wago

Canonical Wago documentation

Compatibility and verification

Exact scope for Wago’s published verification totals, official WebAssembly corpora, and imported wazero tests.

Last synchronized: Wago source: 7d8c58aa454a

Verified result

At Wago commit 7d8c58aa454a, the public verification report records 96,972 passed, 0 failed, and 22 skipped checks on darwin/arm64.

GatePassedFailedSkippedAccounting unit
Normal4,333017Go tests and subtests
Guard pages1,07705Go tests and subtests
Spec 1.016,02600execution assertions
Spec 2.051,211002880 validation + 48331 execution assertions
SIMD24,32500execution assertions

Primary result: public verification

Official WebAssembly suites

Wago pins the WebAssembly MVP and Core 2.0 repositories as git submodules. The public gate reports 16,026 Release 1 execution assertions, 2,880 Release 2 validation assertions, 48,331 Release 2 execution assertions, and 24,325 SIMD execution assertions.

These are assertion counts, not interchangeable “test case” counts. The separate legacy MVP page reports 57/57 applicable files and 16,592 passing assertions under its own older corpus/accounting boundary.

Evidence: public verification · feature matrix

Imported wazero coverage

The claim is not “Wago runs the entire wazero repository unchanged.” Wago audits all 234 upstream Go test files at wazero commit 236c2458ed22, then records each as ported/covered, not applicable, benchmark/example-only, or reviewed without a direct port. Named Wago suites contain copied or adapted semantic cases and pinned fixtures.

The ledger separately accounts for 39 upstream engine cases, 147 Core v2 WAST files, 63 extended-constant artifacts, 782 fail-closed proposal artifacts, 71 fuzz fixtures, and 23 engine fixtures.

Scope and disposition ledger: wazero applicability ledger

Wasmtime suite claim

Not claimed. The current source commit contains differential expectations informed by Wasmtime, but no comparable Wasmtime test-suite import ledger. Wago should not be described as “passing the full Wasmtime suite” on the evidence currently published.

Architecture scope

Linux/amd64, Linux/arm64, and Darwin/arm64 run the native runtime/API, guard-page, and corpus matrix. Core v2 runs on Linux/amd64 and Linux/arm64. The checked-in aggregate verification report itself was generated on Darwin/arm64.

Evidence: native CI matrix · public verification