Supported Frameworks

CodeRadius builds a knowledge graph of a codebase's architecture: services, APIs, databases, and message channels. It combines three extraction methods: tree-sitter AST parsing for deterministic signals (decorators, route registrations, ORM annotations), regex-based entrypoint/connection-string detection, and LLM analysis for anything a parser can't resolve statically. This page lists what's detected for each language, framework, protocol, and infrastructure component, and by which method.

Note: Missing a framework or protocol? coderadius.yaml lets you declare any pattern static analysis can't infer automatically.

TypeScript / JavaScript

AST-level parsing with decorator-based and convention-based (file-path) routing extraction.

Also detected: TypeORM @Entity/EntitySchema (eval-verified), MikroORM, sequelize-typescript, Mongoose/Typegoose/@nestjs/mongoose, Drizzle pgTable/mysqlTable/sqliteTable entities; Bull/BullMQ @Processor/@Process queue consumers, CQRS handlers, @Cron/@Interval/@Timeout scheduled jobs, nest-commander CLI entrypoints; capability decorators for auth, rate-limit, cache, and transactional boundaries; typed API clients via Zodios and urql.

PHP

AST-level parsing with support for PHP 8 attributes, legacy DocBlock annotations, and convention-based routing.

Python

No static route extractor. AST parsing covers functions, imports, and env vars. Routes and ORM models are detected via LLM analysis; a deterministic path validator (validateInboundPath) checks the result and accommodates framework-specific path styles (e.g. Django's optional leading slash).

Go

No static route extractor. Framework recognition is an entrypoint regex (for service classification) plus LLM-driven handler and path detection, checked by the same deterministic path validator used for Python.

Path validation also accommodates Echo, gorilla/mux, and chi route styles; these frameworks have no dedicated entrypoint signal yet. Route groups and middleware are not modeled for any Go router.

Java

Deterministic route extraction from annotations. No cross-file value resolution, DI/bean tracing, or critical-invocation extraction yet. The plugin is a route-extraction bootstrap, not a full semantic layer.

In Development

No language plugin exists yet for these (core/languages/registry.ts currently registers TypeScript, PHP, Python, Go, Java). No route, ORM, or infra extraction until a plugin lands.

API Patterns & Protocols

Databases

CodeRadius detects which databases a service communicates with via ORM configurations, table/collection names extracted from SQL and ORM call sites, and connection endpoint detection in environment files. Credentials are never read or stored. Connection strings are parsed but the user/password fields are deliberately discarded.

Message Brokers

CodeRadius models messaging across three ontological layers so blast radius, governance, and lineage stay correct even on multi-cluster deployments:

• MessageBroker: physical broker instance (cluster, host, vhost, region, env). Identity is fingerprinted on (provider:host:port:vhost) so two clusters with the same nominal name stay distinct.
• MessageChannel with scope ∈ {logical, physical, transport}: logical is the business event (e.g. OrderCreated), physical is the broker address (e.g. exchange acme.orders on rmq-prod-eu), and transport is the Symfony Messenger / Mass Transit / Spring-Cloud wrapper around an underlying physical channel.
• Edges: (LogicalChannel)-[:MANIFESTS_AS]->(PhysicalChannel), (TransportChannel)-[:BACKED_BY]->(PhysicalChannel), (MessageChannel)-[:HOSTED_ON]->(MessageBroker), (MessageChannel)-[:ROUTES_TO {bindingKey, isPattern, patternRegex}]->(MessageChannel), and (MessageChannel)-[:DEAD_LETTERS_TO]->(MessageChannel).

Two safety rules are non-negotiable: strict broker isolation (channels on different brokers are never merged, or "welded", heuristically) and user-declared mirrors only (Shovel / Federation / MirrorMaker convergence requires an explicit message_channels.mirrors[] block in coderadius.yaml).

Provider matrix

Brokers not auto-detected can also be declared explicitly in coderadius.yaml under messageBrokers, with an optional fingerprint override for cases where host/port/vhost can't be inferred from config.

Custom decorator support

NestJS broker decorators (@MessagePattern, @EventPattern, @RabbitSubscribe, @RabbitRPC, @SqsMessageHandler, @SqsConsumerEventHandler, @Process, @Processor) are recognized natively. Custom consumer decorators, configurable per repository, plug in via coderadius.yaml:

decorators:
  - name: AcmeBusConsumer
    kind: message-consumer
    args: [queueName, routingKey, queue, name, topic]

The framework-signal extractor consults the registered decorator name (case-insensitive) and emits a LISTENS_TO edge with the resolved channel name (from the named arg or the first string literal). See Custom decorator registration and Messaging domain model for the full architecture.

CI/CD Platforms

cr blast integrates with any CI system via exit codes and structured output. The table below refers to native pipeline integration: pre-built job templates that run the impact check and post results as a PR/MR comment automatically, without custom scripting.

Configuration File Detection

CodeRadius automatically detects and extracts architectural information from configuration and build files.

Package Manager Detection

CodeRadius detects the specific package manager used per project, not just the ecosystem. This is exposed as ToolConfig nodes in the graph and visible in the System Registry dashboard.

JavaScript / TypeScript

Detection priority:

1. packageManager field in package.json (Corepack standard, e.g. "packageManager": "pnpm@9.15.0")
2. Lockfile presence checked in the same directory, then walking up to the repo root (monorepo-aware)
3. Fallback to npm

PHP

Python

Go

Other manifests

pyproject.toml / requirements.txt (Python) and pom.xml / build.gradle / build.gradle.kts (Java) drive language and manifest detection, not package-manager identification. Python and Java don't have a single-lockfile convention the way JS/PHP/Go do.