genotoxic

What problem does it solve?

Genotoxic turns noisy mutation-testing survivors into clear engineering actions by combining mutation results, necessist (test-statement weakness detection), and code-graph context to determine whether gaps should be fixed with stronger unit tests or with fuzzing.

Core Features & Use Cases

• Graph-informed triage: Uses trailmark graph pre-analysis to reason about reachability, blast radius, privilege boundaries, and complexity.
• Mutation + necessist correlation: Runs mutation testing and (optionally) necessist, then classifies findings into false positives, missing tests, fuzzing targets, or corroborated items when both tools agree.
• Actionable reporting: Produces a structured markdown report (GENOTOXIC_REPORT.md) with bucketed findings and the mutation/necessist source for traceability.
• Fuzzing prioritization from weak tests: Identifies functions where complex or externally reachable behavior is likely under-tested, using necessist “passed after removal” signals.

Quick Start

Read the mutation framework setup for your language, then run the full workflow by building the trailmark graph first, executing mutation testing, optionally running necessist, and finally generating the categorized GENOTOXIC_REPORT.md.