Analyzing .NET assemblies with REA

Last updated: · By the RepoRead editorial team · Unofficial guide
Quick answer

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

LaneManaged-code analysis (.NET PE/CLI)
CLI examplesinspect-managed-artifact, inspect-managed-members
MCP toolsinspect_managed_artifact, inspect_managed_members, plus compare/verify/import tools in the guide
ExecutionNone — static read only
Verified2026-10-18 (UTC)

Shipped tools (summary)

TaskCLI (hyphenated)
Identify artifact / deployment formrea inspect-managed-artifact
Types, signatures, CIL, calls, fieldsrea inspect-managed-members
Declared native calls / indicatorsrea inspect-managed-native-boundaries
Compare members across buildsrea compare-managed-members
Check native decls vs supplied evidencerea 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 CILUnpacking .NET single-file hosts
Declared native dependencies / boundariesDecoding IL2CPP metadata
Build comparisons of managed membersNativeAOT method bodies (needs native analysis)
Absolute-path local files you may readLoading/executing the assembly in-process

Choose the workflow from the artifact's contents, not only the .exe / .dll extension.

Practical workflow

  1. Confirm authorization for the assembly.
  2. Identify the artifact:
rea inspect-managed-artifact /absolute/path/Assembly.dll --json
  1. Inspect members (optionally --type):
rea inspect-managed-members /absolute/path/Assembly.dll --json
  1. For large results, use Evidence views / parent_evidence_id paging as described in the managed-code guide and Evidence explained.

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.

Sources