# oxmutate

> Mutation testing for JavaScript and TypeScript on the oxc engine, run warm inside the project's own Vitest, with CI lanes, SARIF and an agent surface. No dependency outside the burgee family. A Stryker migration path.

## Documentation

- [For agents](https://oxmutate.interlace.tools/docs/agents): What a coding agent reads from oxmutate: one survivor record per mutant with a fix line, the --json envelope, an MCP server with run and survivors as tools, the schema, and exit codes that say whether to rewrite the command.
- [CI lanes](https://oxmutate.interlace.tools/docs/ci-lanes): Run oxmutate in CI the way the work is shaped: only the lines a pull request touched, a run split across a matrix, verdicts reused between runs, and a gate that fails a change which weakened its own tests.
- [Coming from Stryker](https://oxmutate.interlace.tools/docs/coming-from/stryker): Move a Stryker project to oxmutate by changing one command: it reads stryker.config.* unchanged, writes Stryker's JSON report, and runs Stryker's 17 mutator families. What differs on purpose, which keys it does not use, and how closely its verdicts agree with Stryker's.
- [Configuration](https://oxmutate.interlace.tools/docs/configuration): Every key oxmutate reads: Stryker's keys, read from stryker.config.* as they stand, the keys only oxmutate reads, and the Stryker keys it does not use, each with the reason.
- [Getting started](https://oxmutate.interlace.tools/docs/getting-started): Install oxmutate, see the config it reads from your project, run it, and read the survivors back: the lines your tests run but do not check.
- [oxmutate](https://oxmutate.interlace.tools/docs): Mutation testing for JavaScript and TypeScript on the oxc engine, run warm inside the project's own Vitest, with CI lanes, SARIF and an agent surface. No dependency outside the burgee family. A Stryker migration path.
- [Spec oracles](https://oxmutate.interlace.tools/docs/spec-oracles): Replay a formal model's traces against every mutant, as a second verdict beside the tests: Quint's quint run --mbt traces or any directory of ITF files, and a report of each mutant the model catches and the tests miss.

## Family

- [burgee](https://burgee.interlace.tools): the family front door
- [Compatibility](https://burgee.interlace.tools/docs/compatibility): Every drop-in path in the family, graded by the incumbent’s own test suite.
- [Gallery](https://burgee.interlace.tools/docs/gallery): Every glyph, spinner and border the family has registered, rendered.
- [Comparison](https://burgee.interlace.tools/docs/comparison): The family against its incumbents: weight, speed and surface.