Supported Frameworks

CodeRadius performs semantic analysis — not regex matching. It understands framework-specific decorators, routing conventions, ORM mappings, and message dispatch patterns natively. When you ingest a repository, CodeRadius automatically discovers services, APIs, database connections, and message channels without any manual configuration.

TypeScript / JavaScript

Full AST-level parsing with native understanding of decorator-based and convention-based routing.

PHP

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

Python

Full AST-level parsing with native understanding of decorator-based routing and type-hinted dependency injection.

Go

Full AST-level parsing with native understanding of handler registration patterns across major routers.

In Development

The following languages are on the roadmap with active development in progress.

API Patterns & Protocols

Databases

CodeRadius detects which databases a service communicates with via ORM configurations, query patterns, and connection endpoint detection in environment files. Credentials are never read or stored.

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), 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), (MessageChannel)-[:DEAD_LETTERS_TO]->(MessageChannel).

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

Provider matrix

Custom decorator support

NestJS broker decorators (@MessagePattern, @EventPattern, @RabbitSubscribe, @SqsMessageHandler, @Process) are recognized natively. Proprietary or customer-specific consumer decorators (@AliceConsumer, @ConduitHandler, @AcmeBusConsumer, …) plug in via coderadius.yaml:

decorators:
  - name: AliceConsumer
    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 — npm

PHP

Python

Go