Language and framework support

Support describes analysis, not every runtime behavior

The current engineering source includes the ecosystems below. The inventory is based on implemented analyzers, runtime registration, the current support matrix and checked-in validation evidence. It is separate from public release availability. Native product validation is currently evidenced on Windows x64.

TypeScript / JavaScript

Node.js packages, React, Next.js. Includes TS/JS modules and workspace resolution. Dynamic imports, runtime dispatch and full TypeScript type checking are not complete.

Rust

Cargo workspaces. Modules, symbols and explicit source relationships. Macro expansion and type-directed or dynamic dispatch remain partial.

HTML

Static web documents. Source structure and static references. This does not execute a browser or observe the runtime DOM.

CSS

Stylesheets and static assets. Simple selectors, variables and asset relationships. Runtime CSSOM and preprocessor behavior are not executed.

PHP

Composer, Laravel, WordPress. Source and recognizable framework conventions. Runtime hooks, reflection and framework magic remain partial.

Go

Go modules, net/http, Gin, Echo, Fiber, gRPC. Source, module and explicit service relationships. Interface dispatch, build tags and cgo remain partial.

Java

Maven/Gradle, Spring, JAX-RS, JPA/Hibernate, gRPC. Recognizable static declarations and enterprise conventions. Reflection, generated behavior and executable build logic remain partial.

C# / .NET

ASP.NET Core, built-in DI, EF Core, gRPC. Requires the official .NET 10 analyzer package. Reflection, source generators and executable MSBuild behavior remain partial.

Python

Project metadata, FastAPI, Django, Flask, SQLAlchemy, Celery. Source relationships and recognizable framework declarations. Dynamic imports, monkey-patching and runtime metaprogramming remain partial.

Cross-language boundaries

Implemented boundary families include static HTTP, Tauri IPC, generated-style Go/Java/.NET gRPC and Python Celery task relationships. Recognizing a boundary does not fabricate a normal call between two arbitrary language symbols. Python gRPC and a general standalone Protocol Buffers analyzer are not claimed.

Packaging and availability

C# analysis requires the official .NET 10 analyzer package. Other platform installers and distribution details will be described before public access. This guide does not promise that every engineering build contains every optional analyzer or that all frameworks are supported without limits.