---
title: "Check the re-check results for a week’s fix pull requests | Proofline Help"
description: "Open the environment’s weekly report and find Fix pull requests opened to see which fixes received a Kian re-check and what it established."
url: https://proofline.sh/help/weekly-report-fix-rechecks/
---

[Help center](/help/)

# Check the re-check results for a week’s fix pull requests

Open the environment’s weekly report and find Fix pull requests opened to see which fixes received a Kian re-check and what it established.

## Distinguish rule-opened fixes from other pull requests

**Fix pull requests opened** lists every fix pull request opened that week. Kian [re-checks](/help/latent-risk-scans/#read-a-fix-pull-request-s-re-check) only pull requests a fix rule opened, so each finding fix and Fix all pull request reads **Not re-checked**. A fix rule's pull request shows its latest re-check: no counterexample, a counterexample, incomplete with its reason, not finished, or not re-checked. **Latest re-check found no counterexample** counts the fix rule's pull requests whose latest re-check before the week ended found no counterexample. **Re-checked and merged** counts those merged that week after a re-check of the merged commit found no counterexample. Both counts are out of the fix rule's pull requests opened that week, and the report leaves them out when a fix rule opened none. The Slack note's re-check line gives the same **Re-checked and merged** count. No counterexample does not establish that a fix is safe.

Reports kept before re-checks were added omit them and show **Not established**, which names each measure the report could not establish and explains why.

## Related guides

-   [Set up Slack delivery](/help/connect-slack/)
-   [Configure deployment protection](/help/deployment-protection/)
