donnemartin/system-design-primer

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 Findings

The scanner identified 66 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.