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

# Findings and merge score

> Understand the evidence Jina reports and how the merge score summarizes review risk.

# Findings and merge score

Jina turns its investigations into a focused review that engineers can act on before merging.

## Findings

A reported finding is backed by evidence from the review. Depending on the issue, that evidence can include a source trace, a runtime probe, an observed failure, and the code path connected to the behavior.

Jina groups related failures and filters unsupported or low-impact noise. The remaining issues are organized around the bugs that matter, with context such as:

* The behavior that failed.
* The root cause or impact path Jina identified.
* The affected area and source location.
* The issue category and severity.
* Jina's confidence in the evidence.

## Merge score

The merge score is Jina's final risk signal for the pull request after investigation and self-review. It accounts for the traced blast radius, evidence from runtime probes, issue severity, and confidence in the findings.

Use the score as a summary, not a substitute for the issue details. The supporting findings explain what the team should fix, accept, or investigate further before making the merge decision.

## Fewer false positives

Jina does not report every theoretical concern it encounters. It narrows review scope using system context, tests important hypotheses with execution, and reviews its own evidence before returning the result. This is how it aims to surface deeper bugs with less review noise than general coding or static review agents.