> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kong.fyi/llms.txt
> Use this file to discover all available pages before exploring further.

# Evaluating Results

> Score Kong's analysis output against ground-truth source code

## Usage

```bash theme={null}
kong eval ./analysis.json ./source.c
```

`kong eval` compares Kong's output against source code with known function names and signatures. It's useful for benchmarking Kong's accuracy on binaries where you have the original source.

## Example output

```
Binary: binary
Functions: 156 analyzed / 200 in source
Symbol Accuracy: 87.3%
Type Accuracy: 72.1%

Per-Function Scores:
  OK parse_http_header             -> parse_http_header  sym=1.00  type=0.95
  OK handle_connection             -> handle_connection  sym=0.95  type=0.89
  ~~ process_data                  -> process_request    sym=0.60  type=0.45
  NO FUN_00401000                  -> (no match)         sym=0.00  type=0.00
```

## Scoring indicators

| Indicator | Meaning                                        |
| --------- | ---------------------------------------------- |
| **OK**    | Symbol accuracy ≥ 0.8 — good match             |
| **\~\~**  | Symbol accuracy > 0 but \< 0.8 — partial match |
| **NO**    | No match found                                 |

## Symbol accuracy

Kong uses **recall-weighted word matching with synonym expansion** to score function names. Names are split into word tokens (by underscores and camelCase), then scored:

| Score            | Condition                                                           |
| ---------------- | ------------------------------------------------------------------- |
| **1.0**          | Exact string match                                                  |
| **0.9**          | Same word set, different order                                      |
| **0.8**          | All ground-truth words present (superset match, including synonyms) |
| **recall × 0.7** | Partial overlap, scaled by how many truth words are covered         |
| **0.0**          | No overlap, even after synonym expansion                            |

**Synonyms:** Kong recognizes equivalent terms — `search`/`find`/`lookup`, `create`/`make`/`new`/`alloc`, `delete`/`remove`, `buffer`/`buf`, and others. So `find_node` matching against `search_element` would get synonym credit.

## Type accuracy

Type signatures are scored by weighted component matching:

| Component           | Weight | How it's scored                                                     |
| ------------------- | ------ | ------------------------------------------------------------------- |
| **Return type**     | 40%    | Exact match after normalizing Ghidra aliases (`undefined4` → `int`) |
| **Parameter count** | 30%    | Exact match on number of parameters                                 |
| **Parameter types** | 30%    | Per-parameter type match, averaged                                  |

Parameter **names** are not compared — only types. This reflects that parameter naming is subjective, while types are structural.

## Further reading

* [CLI Reference: `kong eval`](/reference/cli/eval) — full flag reference
* [Interpreting Kong Output](/case-studies/interpreting-output) — understanding analysis results