Built with Mutant

Showcase

Every entry here is a document that ships worked material — a diagram, a runnable fence, or both. The list is derived from the corpus, so it tracks the docs rather than a hand-kept feature list.

let parse_record = fn(buf, offset) {
    let magic, magic_err = bytes_slice(buf, 0, 2);
    if (len(buf) < offset + 16) {
        return "", error(
            "record is truncated",           // message
            "evidence.parser",               // context: where it went wrong
            {"offset": offset,               // related: facts, keeping their types
             "available": len(buf),
             "magic": magic}
        );
    }
    return bytes_slice(buf, offset, 16);
};

Reference

Mutant Language Reference

This document is the practical reference for Mutant language features, reserved keywords, and builtins.

languagesyntaxcontrol-flow docs/MUTANT_LANGUAGE_REFERENCE.md

Read it Source ↗

Runnable code Mutant IR / ByteCode Reference Mutant compiles to a flat, linear byte stream. There is no intermediate representation between the AST and the bytecode – the compiler walks the AST and emits bytes directly. Runtime Runnable code Mutant Cookbook Recipes organised by the question you are actually asking, not by which builtin category the answer happens to live in. Reference Runnable code Mutant in 30 minutes By the end of this you will have written a real triage program, run it against a log file, turned it into an encrypted artifact, and built it into a standalone binary you could… Overview

Mini-projects

Diagrams Security Architecture Diagrams (Code-Synced) Visual reference for how Mutant's runtime security pipeline, policy decisions, and probe gates fit together, kept in sync with current code behavior. docs/SECURITY_DIAGRAMS.md ↗ Diagrams + code Process Injection Detection LLD This Low Level Design (LLD) explains how Mutant currently detects process injection-related tampering and how to expand this into a richer, multi-process detector in the future. docs/PROCESS_INJECTION_DETECTION_LLD.md ↗ Runnable code Modules A Mutant program can be more than one file. import loads another .mut file, binds it to a namespace, and links it into the same program. docs/MODULES.md ↗ Diagrams + code Security Low-Level Design (LLD) This document defines the low-level security design for Mutant's bytecode generation, signing, transport, loading, verification, runtime execution, anti-debugging, integrity… docs/SECURITY_LLD.md ↗ Runnable code Mutant WASM REPL Definitive Guide It maps / to index.html and serves .wasm as application/wasm. docs/WASM_REPL_REFERENCE.md ↗ Diagrams Mutant LSP + VS Code Extension Low-Level Design (LLD) This is the implementation-level developer guide for the Mutant language tooling stack. docs/LSP_EXTENSION_LLD.md ↗ Runnable code Graph Database The db builtins embed a property graph database in the mutant runtime for modeling entities and the relationships between them: people and documents in a knowledge graph, or… docs/GRAPH_DATABASE.md ↗ Runnable code Contributing to Mutant Thanks for looking. This document covers what the project expects of a change, the two constraints that are not negotiable, and the handful of house rules that are unusual enough… CONTRIBUTING.md ↗ Runnable code Testing Mutant programs mutant test runs every test.mut file it finds. A test file is an ordinary Mutant program — it is compiled and run the way any program is, so it can import the module it is testing… docs/TESTING.md ↗

Everything here is in the repo

The examples are authored alongside the language. Clone it, run the corpus, and adapt the pieces you need.

Browse repo ↗