ProofDiff · evidence report

What evidence exists for this change?

A local, evidence-based view of changed code, related tests, deterministic checks, and the places that still need human judgment.

access-controlworking tree vs HEAD2026-08-12T00:00:00.000Z4f059fcf9ab5
◐

Partially verified

1 changed files · 1 changed symbols · highest risk medium

Some applicable evidence passed, but no qualified related target produced a non-skipped passing test observation.

Change review queue

Highest-risk files appear first. Expand a file to audit each claim.

src/access.js

modified · +1 −1 · javascript

Partially verifiedmedium risk · 37
function · canDelete

Some applicable evidence passed, but no qualified related target produced a non-skipped passing test observation.

Inspect evidence and reasoning

Evidence

  • test: test

    Repository test command passed, but ProofDiff did not observe which test files it executed.

    high confidence · passing check
  • 1 statically related test-like path

    Related by resolved local import/dependency paths or accepted runner qualification. Static relationship and runner identity are not runtime coverage.

    medium confidence · related test
  • 1 impacted file

    Reachable through resolved reverse import relationships. This is an impact estimate, not proof of runtime behavior.

    medium confidence · static relationship
  • @babel/parser structural analysis

    Parser confidence: high. Structural findings are evidence about code shape, not correctness.

    high confidence · inference
  • Evidence boundary · runner-qualification · opaque-passing-check

    A repository command passed, but no related test-like path was qualified as an exact target for a recognized runner. ProofDiff intentionally failed closed at this boundary. Next action: Use a supported runner convention or explicit runner target so ProofDiff can bind runtime observation to the related test file.

    high confidence · limitation

Why review this

  • Evidence exists but is not connected to a related passing test.
  • Security-sensitive path name warrants focused human review.

Targeted test outcomes

None observed. Related-file presence alone cannot produce “Related test file passed.”

Statically related test-like paths 1

  • test/access.test.js

Calls in changed lines

No parser-observed call site intersects the changed lines.

Estimated impact 1

  • test/access.test.js

Limits

  • Statically related test-like paths were found, but no runner-qualified exact target produced a non-skipped passing test observation.
  • 1 statically related test-like path was not qualified by a recognized runner convention or configuration.

Verification checks

Commands, outcomes, and bounded output from this run.

passedtest: test143 ms

The command exited successfully. package.json script "test".

npm run test --silent
✔ service boots (0.28ms)
ℹ tests 1
ℹ suites 0
ℹ pass 1
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 37.240875

How to read this: The JSON status verified is displayed as “Related test file passed.” It requires a static relationship, runner qualification, explicit target supply, and at least one non-skipped passing test observed for that exact path—not changed-symbol or changed-line execution, mathematical proof, or a guarantee of safety.