Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Skip to main content
Supported inputs
[Both] Map code, schemas, documents, and media with the right extractor and extras.
Graphify supports a growing set of languages and input formats. Parser coverage varies by construct, and specialized extractors may require an optional package. The package manifest lists the current dependencies.
Code and configuration
| Input | Examples | Notes |
|---|---|---|
| General-purpose code | Python, JavaScript, TypeScript, Go, Rust, Java, C, C++, Ruby, C#, Kotlin, Scala, PHP, Swift, Lua, Zig | Local structural extraction; framework and dynamic-language coverage varies. |
| Additional code | Elixir, Julia, Groovy, PowerShell, Fortran, Verilog, Bash | See the repository’s input table for extensions. |
| Web component files | Vue, Svelte, Astro, JSX, TSX | Extraction depends on the file and supported embedded syntax. |
| SQL | Tables, views, foreign keys, joins | Install the sql extra. |
| Terraform / HCL | .tf, .tfvars, .hcl | Install terraform; the graph describes source configuration, not a Terraform plan. |
| OCaml / Common Lisp | .ml, .mli, .lisp, .cl | Install ocaml or commonlisp. |
| Robot Framework | .robot, .resource | Install robot; uses the official Robot parser. |
| Salesforce Apex | .cls, .trigger | Regex-based extraction. |
| Package and MCP manifests | pyproject.toml, go.mod, pom.xml, MCP JSON files | Packages, dependency edges, and server configuration context. |
Documents and media
| Input | Setup |
|---|---|
| Markdown, MDX, text, HTML, reStructuredText | A semantic backend for rich concept extraction. |
| PDFs | pdf extra. |
| Word and Excel | office extra. |
| Google Workspace shortcuts | Authenticated gws CLI and explicit --google-workspace; google extra for Sheets. |
| Images | A backend with the required image capability. |
| Video and audio | video extra; transcription and semantic processing are separate steps. |
Keep the first scan focused
Start with a repository or one documentation folder. Exclude build outputs and dependencies using ignore rules. Add media only when it contributes useful context; transcription and semantic extraction have different resource requirements from a code-only scan.Responses are generated using AI and may contain mistakes.
