genotoxic

AI Community

Skill notes

When to Use

After mutation testing reveals survived mutants that need triage Identifying where unit tests would have the highest impact Finding functions that need fuzz harnesses instead of unit tests Prioritizing test improvements using data flow context Filtering out harmless mutants from actionable ones

When NOT to Use

Codebase has no existing test suite (write tests first) Pure documentation or configuration changes Single-file scripts with trivial logic

Prerequisites

trailmark installed — if uv run trailmark fails, run: DO NOT fall back to "manual verification" or "manual analysis" as a substitute for running trailmark. Install it first. If installation fails, report the error instead of switching to manual analysis. A mutation testing framework for the target language — if the framework

Rationalizations to Reject

Rationalization · Why It's Wrong · Required Action "All survived mutants need tests" · Many are harmless or equivalent · Triage before writing tests "Mutation testing is too noisy" · Noise means you're not triaging · Use graph data to filter "Unit tests cover everything" · Complex data flows need fuzzing · Check entrypoint reachability "Dead code mutants don't matter" · Dead code should be removed · Flag for cleanup

Phase 1: Build Code Graph and Run Pre-Analysis

Parse the target codebase with trailmark and run pre-analysis before mutation testing. Pre-analysis computes blast radius, entry points, privilege boundaries, and taint propagation, which Phase 3 uses for triage. Use the QueryEngine API to build the graph and run pre-analysis: QueryEngine.from_directory("{targetDir}", language="auto")

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Build Code Graph and Run Pre-Analysis

Parse the target codebase with trailmark and run pre-analysis before mutation testing. Pre-analysis computes blast radius, entry points, privilege boundaries, and taint propagation, which Phase 3 uses for triage. Use the `QueryEngine` API to build the graph and run pre-analysis: `QueryEngine.from_directory("{targetDir}", language="auto")`

02
Phase 2: Run Mutation Testing

Select and run the appropriate framework. See references/mutation-frameworks.md for language-specific setup. Capture survived mutants. Each framework reports differently, but extract these fields per mutant:

03
Phase 2b: Run Necessist (Optional)

If the target language is supported (Go, Rust, Solidity/Foundry, TypeScript/Hardhat, TypeScript/Vitest, Rust/Anchor), run necessist to find unnecessary test statements. This runs independently of Phase 2 and can execute in parallel. Filter to findings where the test passed after removal. See

04
Phase 3: Triage Findings

For each survived mutant and each necessist removal, determine its triage bucket using graph data. Necessist removals must first be mapped to a production function (see references/graph-analysis.md).

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.