Domains · 22 languages · 144 framework specs

Truemend speaks
your stack.

Not translated rules: native AST grammars per language, framework-specific anti-pattern specs, and skill overlays for the assistant you already use.

Pick yours

TypeScript

FULL AST · ast-grep

The deepest coverage in the engine: 83 core patterns plus React/Next.js and testing specs.

159
ANTI-PATTERNS
7
FRAMEWORKS DETECTED
FRAMEWORK SPECS
React + Next.jsVueAngularSvelteExpressTanStack QueryTailwind
WHAT IT CATCHES HERE
✗
floating_promise
un-awaited async call whose failure vanishes
✗
any_leak
any spreading through a typed boundary
✗
catch_rethrow
try/catch that swallows nothing and adds nothing
✗
effect_missing_deps
stale closures in React effects
assistant overlays: claude · cursor · copilot · gemini · windsurf · zed
Platform coverage

Runs on the stack you already run.

Cloud platforms are not a language. What matters is whether the engine has a dedicated spec for the surface, or only the language grammar underneath it. Counts below are spec files and pattern counts, so you can check the claim rather than take it. The Microsoft depth is real and the others are thinner; we are not going to pretend otherwise.

Microsoft
13 SPECS · ~338 PATTERNS
DEEPEST COVERAGE
DEDICATED SPECS AND GRAMMARS
C# core 136ASP.NET Core 54Roslyn / StyleCop 29Semantic Kernel 16Azure OpenAI 15EF Core 14Foundry IQ + Fabric 14Blazor 12Azure Functions 11Extensions.AI 10Fabric 10Azure AI Search 8ML.NET 4
SHARED AND LINE-LEVEL SPECS
Azure Terraform 50, PSRule-mirroredPowerShell 7SQL 15YAML structural

The only platform with a dedicated spec per surface rather than generic language rules. Bicep and ARM templates are not parsed; Azure infrastructure is covered through the PSRule-mirrored Terraform detectors.

Amazon Web Services
1 DEDICATED SPEC · 8 PATTERNS
LANGUAGE COVERAGE
DEDICATED SPECS AND GRAMMARS
TypeScriptPythonJavaGoC#Rust
SHARED AND LINE-LEVEL SPECS
Bedrock 8Terraform 8Docker 12Kubernetes 10

Handler and CDK code is parsed with the full grammar for whichever language it is written in. Bedrock is the one AWS-specific spec. CloudFormation is not parsed.

Google Cloud
1 DEDICATED SPEC · 8 PATTERNS
LANGUAGE COVERAGE
DEDICATED SPECS AND GRAMMARS
PythonGoTypeScriptJavaC#
SHARED AND LINE-LEVEL SPECS
Vertex 8Terraform 8Docker 12Kubernetes 10

Service code and the deployment surface are covered by language and by the shared infrastructure specs. Vertex is the one Google-specific spec.

Truemend holds no certification or reseller status with any of these vendors, and claims none. Product names appear here to say which technologies the engine parses. They are trademarks of their owners and imply no endorsement, affiliation, or review.

See it on a real repo →
Industries

Where “code never leaves”
isn’t a feature. It’s the requirement.

Fintech

CASE STUDY

Migration-heavy codebases where half-finished refactors are the norm. Transaction boundaries, auth consistency, and Stripe integration patterns get dedicated specs.

see: fintech migration engagement, before/after scoring across a 200-file sprint

Healthcare

ZERO EGRESS

PHI can’t leave the building. Neither does your code. Run against a self-hosted model and the analysis is fully air-gapped, with an auditable ledger of every change.

function-level egress or none · on-prem binary license available

Defense & government

SOVEREIGN

Offline binary, no telemetry, no cloud dependency. One 74 MB file that runs in a SCIF as happily as on a laptop, and leaves a signed trail of every mend.

works offline · reversible diffs · .truemend/ledger audit trail

AI-native teams

41% AI-AUTHORED

Codebases written at generation speed drift at generation speed. Dedicated AI-slop detection plus 106 patterns across OpenAI, Anthropic, LangChain, and prompt hygiene.

ai_generated_debt is a scored dimension, measured, not vibes