How it works

The audit

Point Truemend at a directory. It reads the supported files in it:

truemend audit src/

This produces findings grouped by severity, with per-function quality scores.

Understanding results

Truemend reports findings at five severity levels:

• Critical: Issues that cause bugs or security holes
• High: Patterns that make the code harder to change
• Medium: Code smells and maintainability concerns
• Low: Style issues and minor improvements
• Info: The lowest-consequence tier. Hidden by default; pass -v/--verbose to see it.

Each finding includes:

• The file and line number
• The pattern that matched
• The fix path (patch, refactor, or rewrite)
• A suggested remediation

Three kinds of fix

Patches: Mechanical changes applied for you. Reversible. The file is re-parsed after the change, and the original is restored if it no longer parses. Validation checks do not prove that a change preserves every aspect of application behavior, so review the diff and run your tests before merging.

truemend fix src/ --apply

Without --apply, fix previews the changes and writes nothing: run it bare first to see the diff, then add --apply to commit it.

Refactors: Known changes with a bounded scope. Reviewed with your team before they land.

Rewrites: Evidence-backed recommendations in the audit. Never applied automatically.

Reporting

A report with per-function scoring, before/after comparisons, and an executive summary:

truemend report --format pdf --client "Acme Corp" --project "Platform" --tier 1

Continuous monitoring

Truemend can run as a check on pull requests in CI:

truemend audit src/ --ci
# exit 0 = pass, 1 = fail, 2 = warning