pragma.vision Your technology observatory

Verification register Compute & Web Infra

Readiness verdict

Wasmtime

A dated reading of what is claimed, reported, and independently verified in the current evidence.

As of
2026-06-28
Revision
1
Method
v1.0.0

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Claimed
90

Public ambition and stated capability

Reported
88

Observed practitioner reporting

Verified
81

Independently supported evidence

Gap
+9

Claimed minus verified

Evidence strength Critical

Decision

What the current evidence supports

Human editorial judgment · 2026-06-28

Adopt with guardrails

Why
Most mature, security-focused, standards-compliant Wasm runtime with full WASI 0.2 + Component Model support and disciplined ~monthly releases with multi-branch security backports; the open risks (freshly-defaulted async surface, ongoing CVEs) are manageable with version pinning and patch hygiene.
Next
Pin to a current stable (>=v46), wire automated advisory tracking + monthly version bumps, and treat newly-defaulted WASI 0.3 async as soak-period code (extra testing/feature-gating) until it has shipped a few stable cycles.

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
6
Tier 1
0
Tier 2
2
Tier 3
4
Supports
3
Contradicts
1
Context
2
Latest observed
2026-06-25

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Revisions

Initial public reading

This is the initial public reading. No earlier readiness change is recorded.

Your opinion

Tell us anything.

What works, what doesn't, what's missing — especially about our watches, lenses, and the register itself. Anonymous is fine; leave an email if you'd like a reply.