witforge

WIT-first contract compiler for stable Rust, protobuf, JSON Schema, and versioned adapters

View the Project on GitHub asamarts/witforge

Choosing witforge

Good fit

witforge fits when:

Typical examples are analyzers, validators, bounded policy calls, transformation requests, and plugin operations that take and return finite values.

Use another tool directly

Use wit-bindgen and a Component Model runtime when you only need guest/host bindings and Canonical ABI support.

Use protobuf tooling directly when protobuf is already authoritative and WIT is only a generated view.

Use an application runtime or protocol framework for:

witforge does not own those concerns.

Current subset

Supported: records, variants, enums, flags, aliases, lists, options, results, named interface functions, worlds, and standard deps/ package references.

Refused: resources and handles, maps, tuples, chars, fixed-length lists, futures, streams, async functions, accessors, and world-defined functions/types.

Run witforge check against the actual package for the authoritative answer.