WireForge

Schema-driven wire-format toolkit for C++17 and C99: describe binary messages in YAML (by hand, in the web UI, through the CLI or an AI agent) and generate allocation-free serializers, validators, framers and dispatchers (C++17, or C99 with --language c) together with a GoogleTest project that proves them against a reference codec and gates the generated code at 100 % line, branch and function coverage.

• The wire format is imposed by the remote party: generated code never adds bytes.
• Runtime and generated code use only pre-allocated storage: no heap, no exceptions, no RTTI required.
• One service layer behind the wireforge CLI, the Python API, the REST server with its web UI and the MCP server.
• A generated Wireshark Lua dissector shows every interface's frames, with the same checks as the decoder.
• Zero warnings from every compiler and analyzer; tested on 32/64 bit, little and big endian, x86 and ARM, on Linux, Windows, macOS, Android and FreeRTOS; differential testing and fuzzing.

The way in is short: wireforge init gives a working first project, you change it to your protocol, generate the C++ code, run the tests and read the results. Nothing about requirements or standards is needed for that.

For teams with a development or assurance process

Optionally, wireforge docs turns the same model into requirements, design, test and traceability documents with test and coverage results, change impact between revisions and ReqIF/CSV exchange with requirements tools (docs/LIFECYCLE.md, docs/integration/). For projects that apply standards such as DO-178C, ISO 26262, IEC 61508 or IEC 62304, this evidence supports your processes and your tool assessment; it does not by itself give conformity, certification or tool qualification, which depend on the whole project and its assessor (docs/DO178C.md).

Start with the tutorial (a MAVLink 2 drone link from the model to the application, tests, CI, Wireshark and AI agents), docs/GUIDE.md (install, 5-minute quickstart, examples), or the wiki for a short tour. Reference:

Development: see CONTRIBUTING.md (pip install -e ".[dev]", cmake --preset dev && cmake --build --preset dev && ctest --preset dev, all gates: quality/run_all.sh).

GitHub Action

oguzhankynk/wireforge is also a GitHub Action that validates a project, checks wire compatibility with the base of a pull request and runs the generated tests (docs/integration/github_actions.md):

- uses: oguzhankynk/wireforge@v0.3.0
  with: { project: icd }

License

The runtime/ library is MIT-licensed (see runtime/LICENSE): code generated by WireForge belongs to you and depends only on this MIT-licensed runtime, so shipping it in your product carries no restriction.

Everything else (the CLI, code generator, server, web UI, and MCP server) is licensed under the Business Source License 1.1 (see LICENSE): free for development, testing, and evaluation; a commercial license is required for production use, except that running it in continuous integration (validation, comparison with earlier revisions, generated tests) is free, also in commercial product repositories. It converts to MIT on 2036-10-17. Contact the Licensor for commercial licensing: kaynak.oguzhan0@gmail.com.