• ModularityKit.Mutator - core mutation runtime
• ModularityKit.Mutator.Governance - request lifecycle, approvals, and governed execution
• ModularityKit.Mutator.Governance.Redis - Redis provider for ModularityKit.Mutator.Governance

• Examples
• Benchmarks
• Docs
• Tests

Use the root Taskfile.yml with task as the preferred entrypoint for repeated local workflows:

task build
task test
task test:smoke
task docs
task verify

Run task --list-all from the repository root to see the full task surface.

dotnet build ModularityKit.Mutator.slnx -c Release

Run these after dotnet restore ModularityKit.Mutator.slnx:

python3 -m scripts.dependencies.check_package_health --solution ModularityKit.Mutator.slnx

The check reports vulnerable packages as a failing condition and prints outdated packages for review. When a package needs attention, update the affected PackageReference version in the owning project and rerun the check.

Build the DocFX site locally with:

dotnet tool update -g docfx
dotnet build ModularityKit.Mutator.slnx -c Release
docfx docfx.json

The generated site includes the conceptual docs under Docs/ and the public API reference for the three published packages.

The published site is deployed from main to GitHub Pages:

https://modularitykit.github.io/ModularityKit.Mutator/

Release packages can be signed and verified in the standard package publish workflow when signing secrets are configured. Without signing secrets, the attested release path still emits GitHub artifact attestations. See Docs/Package-Signing.md for the signing approach, optional secrets, and local verification expectations.