11 added, 4 removed. Audit A to A.
---
name: dotnet-inspect-correctness
version: 0.1.0
description: Judge whether code is sound and safe to call — its exception surface (throws, catches, exception types) and the unsafe operations in a method body.
---
# dotnet-inspect: correctness and safety
Use this skill to judge whether code is sound and safe to call: what it can
throw, how it handles errors, and where it steps outside safe, managed
execution. This is single-version analysis; for how these signals *change*
between versions, use the compatibility skill.
```bash
dnx dotnet-inspect -y -- <command>
```
## What can it throw? (exception surface)
There is no dedicated "Exceptions" section; exception behavior comes from
- method-body analysis. Project the exception signals as graph fields, or read the
- method's hidden facts:
+ method-body analysis. `Exception Regions` shows the exact catch/filter/finally
+ layout; graph fields and hidden facts summarize behavior:
```bash
+ dnx dotnet-inspect -y -- member Type Method:1 -S "Exception Regions"
dnx dotnet-inspect -y -- member Type Method:1 -S "Call Graph" --fields "Throws,ThrowSites,ExceptionTypes,ConstructedExceptions,Catch,Finally"
dnx dotnet-inspect -y -- member Type Method:1 -S "Call Graph" --fields "Throws,Catch,Finally"
dnx dotnet-inspect -y -- member Type Method:1 -S Facts --tsv
```
`Throws`/`ThrowSites` count throw sites; `ExceptionTypes`/`ConstructedExceptions`
- name the exception types; `Catch`/`Finally` show handling. `-S Facts` (member,
- single method) lists the hidden facts in the body and supports `--tsv`.
+ name the exception types; `Catch`/`Finally` show handling. `Exception Regions`
+ retains IL ranges and caught types. `-S Facts` (member, single method) lists the
+ hidden facts in the body and supports `--tsv`.
## Is it memory-safe? (unsafe operations)
```bash
dnx dotnet-inspect -y -- member Type Method:1 --library MyLib.dll -S "Unsafe Operations,IL"
```
`-S "Unsafe Operations"` shows the unsafe operations in a single method body,
with IL evidence. For the library-wide safety *surface* (unsafe members, P/Invoke
methods) and provenance/supply-chain signals, see the `signals` skill.
+
+ For one crash or profiler coordinate, use `library --il-offset
+ 0x06000001+0x5` for the default source-location, member, instruction, exception,
+ callsite, and return-address context. Safety evidence is opt-in:
+ `--il-offset 0x06000001+0x5 -S "Context: Safety"`.
To confirm whether one definite unsafe operation appeared at an adjacent
version boundary, first correlate caller-selected package cells:
```bash
dnx dotnet-inspect -y -- timeline --package MyLib@1.0.0..2.0.0 \
-t MyType -m Method \
--finding analysis.unsafety --at first --at last
```
Repeat `--at` for sparse probes or use `--at all` for an explicitly bounded
dense traversal. A gap-spanning `Added` row locates a candidate boundary; it
does not claim the exact introduction version. Confirm the adjacent pair:
```bash
dnx dotnet-inspect -y -- diff --package MyLib@1.4.0..1.5.0 \
-t MyType -m Method \
--finding analysis.unsafety
```
`PairFinding.Added` is the introduction proof. `Present` and `Removed`
distinguish persistence from disappearance; the command compares only the two
supplied endpoints.