mirage-analyzer 1.0.2

Path-Aware Code Intelligence Engine for Rust
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92

# Mirage

[![Crates.io](https://img.shields.io/crates/v/mirage-analyzer)](https://crates.io/crates/mirage-analyzer)
[![Documentation](https://docs.rs/mirage-analyzer/badge.svg)](https://docs.rs/mirage-analyzer)

**Version:** 1.0.2

Path-aware code intelligence engine for Rust. Analyzes control-flow graphs to find execution paths, dead code, and impact zones.

**Positioning:** CFG analysis tool for codebases indexed by Magellan. Answers questions like "what code MUST execute on any path from entry to exit?"

## Purpose

**Mirage analyzes control-flow graphs from Magellan.** Built for:

- **Developers** — Find dead code, understand execution paths, analyze impact of changes
- **AI Assistants** — Structured path analysis for code reasoning
- **Tooling** — Scriptable CFG analysis with precise block-level data

## Features

- **Path enumeration** — Find all execution paths through a function
- **Dominance analysis** — Compute dominators, post-dominators, dominance frontiers
- **Loop detection** — Identify natural loops within functions
- **Dead code detection** — Find unreachable blocks
- **Impact analysis** — Blast zones, program slicing
- **Hotspots** — Risk scoring based on path counts and complexity

## Quick Start

```bash
# Install
cargo install mirage-analyzer

# Requires Magellan database (create first)
magellan watch --root ./src --db code.v3

# Check database status
mirage status

# Show execution paths through a function
mirage paths --function "my_crate::process"

# Find unreachable code
mirage unreachable

# Visualize control flow
mirage cfg --function "my_crate::main" --format dot
```

## Installation

```bash
cargo install mirage-analyzer
```

Or build from source with Native-V3 backend:

```bash
# Native-V3 backend (recommended - fastest)
cargo install mirage-analyzer --features native-v3 --no-default-features
```

## Backends

| Feature | Description | File | Best For |
|---------|-------------|------|----------|
| `native-v3` | **High-performance binary backend** | `.v3` | Production (recommended) |
| (default) | SQLite backend | `.db` | Compatibility |

Both backends provide identical CFG analysis results.

## Requirements

- **[Magellan](https://github.com/oldnordic/magellan)** 2.4.3+ — Required for CFG extraction
- **[sqlitegraph](https://crates.io/crates/sqlitegraph)** 2.0.3+ — Included automatically

## Documentation

- **[MANUAL.md](MANUAL.md)** — Complete command reference and examples
- **[CHANGELOG.md](CHANGELOG.md)** — Version history

## What Mirage Does NOT Do

- ❌ Search code (use [llmgrep](https://github.com/oldnordic/llmgrep))
- ❌ Index code (use [Magellan](https://github.com/oldnordic/magellan))
- ❌ Type checking or semantic analysis
- ❌ Code editing (use [splice](https://github.com/oldnordic/splice))

## License

GPL-3.0-or-later. See [LICENSE](LICENSE).