Project Review
Within the current Python static-analysis scope; this is not a proof of total correctness.
Start here: review confirmed findings first; then inspect the highest review-breadth targets before making broad changes.
What needs attention?
What should I review if I change this?
Where is the evidence?
Review first
Review breadth is prioritization metadata, not defect truth.
| # | Target | Breadth | Files | State coupled | Boundaries |
|---|---|---|---|---|---|
| 1 | tests/test_a.py | 10 | 4 | 1 | 3 |
| 2 | a.py | 10 | 4 | 1 | 3 |
| 3 | b.py | 10 | 4 | 1 | 3 |
| 4 | c.py | 10 | 4 | 1 | 3 |
| 5 | 2 | 1 | 2 | 0 | |
| 6 | b.py | 1 | 1 | 1 | 0 |
Current findings
Confirmed defects: 0
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
| Severity | Class | Type | Location | Symbol | Evidence statement |
|---|---|---|---|---|---|
| No findings in the current static scope. | |||||
Impact Review
Direct means one-hop graph evidence. Derived means bounded resolved call paths plus shared-state coupling.
Functional shapes
| Motif | Instances |
|---|---|
| resource_scope | 1 |
| read_modify_write | 1 |
Program structure
Resolved local calls: 3
Boundary calls: 3
State regions: 1
State writes: 1
Effect relations: 1
Source identity
| Path | Bytes | SHA-256 |
|---|---|---|
| a.py | 57 | ed421b0a3ed16047e2… |
| b.py | 238 | a9af3ee8d84e48ef8e… |
| c.py | 30 | a9809ee1c71cf4fb1e… |
| tests/test_a.py | 62 | 3c5756cfd4cc615df1… |
Epistemic boundary
- 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
- local call target resolution
- parameter-container state regions
- effect hints
- branch/loop phi merges
- explicit exception catch matching
- structural motif candidates
- runtime dispatch
- reflection
- native extension behavior
- external library semantics
- precise heap points-to beyond definition-time alias
- dynamic exception behavior from calls
- concurrency semantics