AI Slop Code RIsk Monitor

sebastianbergmann/object-reflector

Allows reflection of object attributes, including inherited and non-public ones

8.0 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for sebastianbergmann/object-reflector, a PHP project with 6,272 GitHub stars. SynthScan examined 1,750 lines of code across 29 source files, recording 14 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 8.0 (Moderate pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

8.0
Adjusted Signal
8.0
Raw Pattern Score
100%
Time Factor
2026-10-09
Last Push
6.3K
Stars
PHP
Language
1.8K
Lines of Code
29
Files
14
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 33.0/100 · MEDIUM

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 33.0/100 · MEDIUM

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

PR Review Velocity Impact 33.0/100 · MEDIUM

Which changes need focused human review? 14 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

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

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 0MEDIUM 0LOW 14

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 14 distinct pattern matches across 1 syntactic category. 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.

Hyper-Verbose Identifiers14 hits · 14 pts
SeverityFileLineSnippetContext
LOWtests/unit/ObjectReflectorTest.php36 public function testReflectsAttributesOfObject(): voidCODE
LOWtests/unit/ObjectReflectorTest.php54 public function testReflectsAttributeWithIntegerName(): voidCODE
LOWtests/unit/ObjectReflectorTest.php66 public function testReflectsProtectedAndPublicPropertiesOfObject(): voidCODE
LOWtests/unit/ObjectReflectorTest.php82 public function testReflectsPrivatePropertyThatIsRedeclaredInChildClass(): voidCODE
LOWtests/unit/ObjectReflectorTest.php102 public function testUnmanglesPropertyNameBasedOnClassOfReflectedObject(): voidCODE
LOWtests/unit/ObjectReflectorTest.php126 public function testReflectsPropertiesOfObjectOfAnonymousClass(): voidCODE
LOWtests/unit/ObjectReflectorTest.php140 public function testDoesNotReflectUninitializedProperty(): voidCODE
LOWtests/unit/ObjectReflectorTest.php159 public function testReflectsValueStoredInBackedPropertyWithHooksAndIgnoresVirtualProperty(): voidCODE
LOWtests/unit/ObjectReflectorTest.php173 public function testReflectsPropertyWhoseNameContainsNullByte(): voidCODE
LOWtests/unit/ObjectReflectorTest.php185 public function testReflectsPropertyWhoseNameBeginsWithNullByte(): voidCODE
LOWtests/unit/ObjectReflectorTest.php197 public function testReflectsPropertyWhoseNameIsEmpty(): voidCODE
LOWtests/unit/ObjectReflectorTest.php209 public function testReflectsObjectWithoutProperties(): voidCODE
LOWtests/unit/ObjectReflectorTest.php221 public function testDoesNotInitializeLazyObject(): voidCODE
LOWtests/unit/ObjectReflectorTest.php241 public function testReflectsPropertiesOfInitializedLazyObject(): voidCODE