ProofDiff maps changes to statically related test-like paths, qualifies exact runner targets, and shows which paths produced non-skipped tests.
test/access.test.js is statically related, but ProofDiff did not observe a passing test for that exact target.
Every result below comes from an actual Git diff and actual ProofDiff execution. Passing, zero-test, missing, unsupported, and failing evidence all stay visible.
A qualified related JavaScript target produces a passing test observation; a Python retry change has no applicable verification.
PARTIAL · highest risk HIGH · 2 files · 2 symbols UNVERIFIED services/email.py HIGH 58 Evidence: none observed; status is not a safety claim. RELATED TEST FILE PASSED src/discount.js LOW 10Open full evidence report →
The repository test command passes while excluding the related test. ProofDiff keeps the changed file only partially verified.
PARTIAL · highest risk MEDIUM · 1 file · 1 symbol PARTIAL src/access.js MEDIUM 37 Evidence: test: test — Repository test command passed, but ProofDiff did not observe which test files it executed.Open full evidence report →
A tax calculation regression is connected to a related test that executes and fails.
FAILED · highest risk CRITICAL · 1 file · 1 symbol FAILED src/tax.js CRITICAL 80 Evidence: targeted node-test: 1 qualified test target: test/tax.test.js — ProofDiff explicitly supplied this runner-qualified target. The runner observed 0 passed, 1 failed, and 0 skipped test for this exact target.Open full evidence report →
A Rego policy change has no language adapter or discovered check, so the report stays explicitly unknown.
UNKNOWN · highest risk HIGH · 1 file · 0 symbols UNKNOWN policy/access.rego HIGH 75 Evidence: none observed; status is not a safety claim.Open full evidence report →