Analyzing .NET assemblies with REA
REA 6.5.0 ships a static .NET lane that inspects PE/CLI assemblies: identity, metadata, CIL instructions and declared native dependencies — without loading or executing the code and without a native analysis engine.
rea inspect-managed-artifact /absolute/path/Assembly.dll --json
rea inspect-managed-members /absolute/path/Assembly.dll --json
rea inspect-managed-members /absolute/path/Assembly.dll --type Example.Parser --json
Upstream guide: managed-code-analysis.md. RepoRead is unofficial.
Project facts
inspect-managed-artifact, inspect-managed-membersinspect_managed_artifact, inspect_managed_members, plus compare/verify/import tools in the guideShipped tools (summary)
| Task | CLI (hyphenated) |
|---|---|
| Identify artifact / deployment form | rea inspect-managed-artifact |
| Types, signatures, CIL, calls, fields | rea inspect-managed-members |
| Declared native calls / indicators | rea inspect-managed-native-boundaries |
| Compare members across builds | rea compare-managed-members |
| Check native decls vs supplied evidence | rea verify-managed-native-boundaries |
Canonical names use underscores in MCP (inspect_managed_artifact). See the generated catalog.
Scope limits (read before you assume)
| Supported (static) | Not this lane |
|---|---|
| Regular PE/CLI metadata and CIL | Unpacking .NET single-file hosts |
| Declared native dependencies / boundaries | Decoding IL2CPP metadata |
| Build comparisons of managed members | NativeAOT method bodies (needs native analysis) |
| Absolute-path local files you may read | Loading/executing the assembly in-process |
Choose the workflow from the artifact's contents, not only the .exe / .dll extension.
Practical workflow
- Confirm authorization for the assembly.
- Identify the artifact:
rea inspect-managed-artifact /absolute/path/Assembly.dll --json
- Inspect members (optionally
--type):
rea inspect-managed-members /absolute/path/Assembly.dll --json
- For large results, use Evidence views /
parent_evidence_idpaging as described in the managed-code guide and Evidence explained.
Related on RepoRead
- Evidence explained · CLI cheat sheet · REA vs opening Ghidra yourself · Errors · What is REA? · Install
FAQ
Does REA execute my DLL?
No. The managed lane reads PE/CLI metadata and CIL without loading or executing the assembly.
Do I need dnSpy or Ghidra?
Not for static metadata/CIL inspection. NativeAOT method bodies and native bridges need native analysis; IL2CPP metadata is out of this parser's scope.
What about single-file .NET publishes?
Upstream states the managed parser does not unpack .NET single-file hosts. Identify the deployment form with inspect-managed-artifact first.
How do I focus on one type?
Pass --type with an exact full_name from member inspection (repeatable). Omitting --type inspects all members (output can be large).
Is this for bypassing .NET licensing?
No. Authorized assemblies only. Protection bypass is explicitly out of scope in REA's disclaimer.