Repository Semantic Review v0.7
/mnt/data/PBSOI_CISG_MVP_v0.7/semantic_diff_demo/target
Technical evidence view →

Project Review

● 1 confirmed defect

Confirmed by current deterministic rules in the analyzed static scope.

Analysis cache: full_recompute

Start here: review confirmed findings first; then inspect the highest review-breadth targets before making broad changes.

What this answers

What needs attention?

What should I review if I change this?

Where is the evidence?

4
Files
4
Functions
1
Confirmed defects
0
Hotspots
1
State regions
3
Boundary calls
2
Motifs
2
Resolved calls

Review first

Review breadth is prioritization metadata, not defect truth.

#TargetBreadthFilesState coupledBoundaries
1
app.py
8303
2
extra.py
7203
3
helper.py
7203
4
1110
5
bad.py
0100

Current findings

Confirmed defects: 1

Anomalies: 0

Hotspots: 0

A hotspot means “review-worthy,” not “wrong.” Unknown remains unknown.

Scope

Repository → semantic graph → data/state closure → impact → findings

Python-only, static-first. Dynamic dispatch, reflection, native behavior, precise runtime path probability, and concurrency remain outside the current strong claim.

Findings

SeverityClassTypeLocationSymbolEvidence statement
highdefectpossibly_undefined_localbad.py:4brokenLocal variable 'value' may be undefined on at least one reaching control-flow path.

Impact Review

Direct means one-hop graph evidence. Derived means bounded resolved call paths plus shared-state coupling.

Functional shapes

MotifInstances
resource_scope1
read_modify_write1

Program structure

Resolved local calls: 2

Boundary calls: 3

State regions: 1

State writes: 1

Effect relations: 1

Open full node/data/state graph

Source identity

PathBytesSHA-256
app.py2242ec088553b6e6f879a…
bad.py66fa44a6a601b5f7c68d…
extra.py29447d7f48d560011b5f…
helper.py32ae12b83043de4abfc4…

Epistemic boundary

observed
  • Python AST definitions
  • imports
  • call syntax
  • control syntax
  • source spans
  • local file hashes
  • SSA-like local definitions/uses
  • self/cls/explicit-global state accesses
  • module-binding reads
  • explicit raise/except syntax
  • definition-time Python name aliases
strongly_inferred
  • local call target resolution
  • parameter-container state regions
  • effect hints
  • branch/loop phi merges
  • explicit exception catch matching
  • structural motif candidates
unresolved
  • runtime dispatch
  • reflection
  • native extension behavior
  • external library semantics
  • precise heap points-to beyond definition-time alias
  • dynamic exception behavior from calls
  • concurrency semantics