cdyforever/how-to-live-better

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 0.0/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 0 finding(s).

Hallucinated Dependency & Supply Chain Risk 91.0/100 · CRITICAL

Are imports declared and package/API names verified? 8 finding(s).

Agent Over-Engineering Ratio 41.4/100 · MEDIUM

Are wrappers, guards, and repeated structures necessary? 3 finding(s).

PR Review Velocity Impact 97.1/100 · CRITICAL

Which changes need focused human review? 11 finding(s).

What These Metrics Mean

Adjusted Signal: Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score: Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor: A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits: Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate: High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files: Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 8MEDIUM 1LOW 2

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 11 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Cross-Language Confusion7 hits · 35 pts

Severity	File	Line	Snippet	Context
HIGH	build.py	406	let grade=null, plainOnly=false;	CODE
HIGH	build.py	428	const nodes=[]; while(w.nextNode()) nodes.push(w.currentNode);	CODE
HIGH	build.py	452	if(grade && c.dataset.grade!==grade) ok=false;	CODE
HIGH	build.py	453	if(ok && term && !c.textContent.toLowerCase().includes(term)) ok=false;	CODE
HIGH	build.py	473	let timer=null;	CODE
HIGH	build.py	476	grade=(mode==='A')?'A':null;	CODE
HIGH	build.py	535	else if(jump && e.target.tagName==='SECTION')	CODE

Empty Error Handlers1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	build.py	170	except Exception:	CODE

Excessive Try-Catch Wrapping2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	build.py	170	except Exception:	CODE
MEDIUM	build.py	119	def ratio_of(t):	CODE

Unused Imports1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	build.py	23		CODE