Graphtia documentation · reference
Language and framework support
Current analysis-engine coverage, packaging requirements and important static-analysis limits.
Support describes analysis, not every runtime behavior
Explorer recognizes ten language ecosystems, including conditional C-family analysis. TypeScript, JavaScript, TSX and JSX share one ecosystem; prepared Arduino belongs to C/C++. SQL and OpenAPI are separate declaration formats. A supported language does not mean every dynamic behavior or framework convention can be resolved. Check the coverage notices and packaged analyzers in your installed version.
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. Explorer can inspect source arguments of a bounded subset of standard assertion, formatting/printing, vec! and matches! macros, preserving their original locations. It does not expand macros. Shadowing and ambiguous imports remain conservative; type-directed and dynamic dispatch are 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 and generated-style gRPC. Graphtia’s Roslyn-based C# analyzer is bundled self-contained in official .NET-enabled Explorer packages; no separate analyzer installation is needed. Reflection, source generators, runtime dispatch 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
Graphtia’s Roslyn-based C# analyzer is bundled self-contained in official .NET-enabled Explorer packages. A separate analyzer or .NET runtime installation is not needed for those packages. C-family analysis uses its matching packaged helper and prepared compilation context. Free access has the features and limits shown in your account; product access does not remove analyzer or static-analysis limits.
Database code and declaration formats
Database declarations cover bounded PostgreSQL, MySQL and SQLite SQL. Separate TypeScript/JavaScript and Python adapters recognize supported database uses in source. OpenAPI 3.0 and 3.1 JSON/YAML describe API declarations. SQL and OpenAPI are declaration formats, not additional general-purpose language analyzers.
Choose the dedicated database and API guides for their supported forms, source evidence and limitations. No database connection, SQL execution, migration application, live HTTP request or external reference fetch is performed by these readers.
C, C++ and prepared Arduino
C-family analysis is partial and requires the official packaged analyzer plus the supplied compilation context. It can expose supported declarations, references, calls and type relationships. Header interpretation follows its translation unit. Imported compiler commands are read as data; Explorer does not execute a build.
Arduino support requires prepared generated C++, explicit board/core/header context and validated mapping back to the original sketch tabs. It does not mean an arbitrary sketch, every board or an unprepared ESP32 project can be analyzed. Missing preparation remains a limitation rather than guessed relationships.
Framework support is specific to patterns
React/Next.js, WordPress, Laravel, Go service frameworks, Java enterprise frameworks, .NET frameworks and Python frameworks provide different static enrichments. Recognizing an ORM model is not the same as proving a code-to-SQL-table link. Driver names, framework adapters and language ecosystems are different inventories; none implies support for every version or plugin.
Detailed framework coverage
Go beyond language recognition: review exactly which routes, components, services, model mappings and tasks each framework adapter can expose.
How parsing becomes an explorable graph
Graphtia builds on established parsers and compiler libraries: Oxc for TypeScript and JavaScript, syn for Rust, Tree-sitter for HTML, PHP, CSS, Go, Java and Python, Roslyn for C#, and libclang for C/C++. Graphtia’s analysis layers extract and normalize code facts, resolve supported relationships, add framework and contract knowledge, and attach source evidence to an explorable graph. Coverage depends on the language, recognized constructs and available project context; dynamic behavior and ambiguous targets can remain unresolved.
Unsupported files are not files without dependencies
The coverage classifier recognizes source families including Lua, Ruby, R, Elixir, Erlang, Haskell, Clojure/CLJS, Swift, Scala, Dart, Zig and Perl without a compatible official language analyzer. An omitted file does not mean it contains no symbols or relationships.
Kotlin source, Python .pyi stubs and Vue/Svelte single-file components do not have an official semantic analysis route. Recognizing Gradle Kotlin metadata is not Kotlin language support. Not every unsupported extension is necessarily listed in the coverage report.
Review the available coverage and diagnostics alongside the indexed files. Separate unsupported source, excluded files and analyzed code before interpreting an empty graph or planning a change.