Home / bvaughn / react-virtualized
AI Slop Code Risk Monitor

bvaughn/react-virtualized

SlopCodeMonitor badge for bvaughn/react-virtualized Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for bvaughn/react-virtualized. SynthScan examined 48,484 lines of code across 301 source files, recording 33 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.7 (Low 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.

0.7
Adjusted Signal
0.7
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
48.5K
Lines of Code
301
Files
33
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

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

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 3.4/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 2.6/100 · LOW

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

PR Review Velocity Impact 3.4/100 · LOW

Which changes need focused human review? 33 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 0MEDIUM 0LOW 33

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 33 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.

Hyper-Verbose Identifiers26 hits · 26 pts
SeverityFileLineSnippetContext
LOWintegrations/tests/tests/utils.ts138export async function expectVisibleRowsRendered(CODE
LOW…tegrations/tests/tests/scroll-element-masonry.spec.tsx65async function expectVisibleCellsRendered(page: Page) {CODE
LOWintegrations/tests/tests/scroll-element-grid.spec.tsx38async function expectVisibleColumnsRendered(page: Page) {CODE
LOWlib/utils/scrollElement/scrollListeners.ts32function enablePointerEventsIfDisabled() {CODE
LOWlib/utils/scrollElement/scrollListeners.ts44function enablePointerEventsAfterDelayCallback() {CODE
LOWlib/utils/scrollElement/scrollListeners.ts49function enablePointerEventsAfterDelay() {CODE
LOWlib/components/CellMeasurer/CellMeasurer.test.tsx49function mockSizesFromDataAttributes() {CODE
LOW…/components/CellMeasurer/CellMeasurer.react18.test.tsx13function mockSizesFromDataAttributes() {CODE
LOWlib/components/MultiGrid/MultiGrid.test.tsx956 function getDeferredMeasurementCache() {CODE
LOWlib/components/MultiGrid/MultiGrid.tsx362function createDeferredMeasurementCaches(CODE
LOWlib/components/InfiniteLoader/utils.ts125export function forceUpdateReactVirtualizedComponent(CODE
LOWlib/components/List/List.test.tsx88 function getInnerScrollContainerHeight() {CODE
LOWlib/components/Grid/Grid.test.tsx113 function createScrollDirectionTracker() {CODE
LOWlib/components/Grid/defaultOverscanIndicesGetter.ts14export function defaultOverscanIndicesGetter({CODE
LOW…/components/Grid/accessibilityOverscanIndicesGetter.ts14export function accessibilityOverscanIndicesGetter({CODE
LOW…/components/Grid/utils/updateScrollIndexHelper.test.ts7export function getCellSizeAndPositionManager({CODE
LOW…mponents/Grid/utils/CellSizeAndPositionManager.test.ts6 function getCellSizeAndPositionManager({CODE
LOW…mponents/Grid/utils/CellSizeAndPositionManager.test.ts254 function getUpdatedOffsetForIndexHelper({CODE
LOWsrc/routes/hoc/examples/ArrowKeyStepperControlled.tsx19function ArrowKeyStepperControlled({ width }: { width: number }) {CODE
LOW…/routes/cell-measurer/CellMeasurerLimitationsRoute.tsx4export default function CellMeasurerLimitationsRoute() {CODE
LOW…routes/cell-measurer/CellMeasurerColumnWidthsRoute.tsx8export default function CellMeasurerColumnWidthsRoute() {CODE
LOWsrc/routes/masonry/MasonryCellPositionersRoute.tsx7export default function MasonryCellPositionersRoute() {CODE
LOWsrc/routes/masonry/examples/MasonryCustomPositioner.tsx13function createRoundRobinPositioner(columnCount: number, columnWidth: number) {CODE
LOWsrc/routes/guides/MultiColumnSortTableRoute.tsx15export default function MultiColumnSortTableRoute() {CODE
LOWsrc/routes/list/ListVariableRowHeightsRoute.tsx6export default function ListVariableRowHeightsRoute() {CODE
LOW…/routes/window-scrolling/ScrollingWithThePageRoute.tsx22export default function ScrollingWithThePageRoute() {CODE
Structural Annotation Overuse4 hits · 6 pts
SeverityFileLineSnippetContext
LOWCHANGELOG.md729###### Step 1: Rename components (`FlexColumn`, `FlexTable`, `VirtualScroll`)COMMENT
LOWCHANGELOG.md750###### Step 2: Update cell and row renderersCOMMENT
LOWCHANGELOG.md778###### Step 3: Update cell/row CSS class names and stylesCOMMENT
LOWCHANGELOG.md834###### Step 4: Update CSS class namesCOMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWsrc/utils/data.ts161 "Lorem ipsum dolor sit amet, consectetur adipiscing elit.",CODE
LOWsrc/utils/data.ts161 "Lorem ipsum dolor sit amet, consectetur adipiscing elit.",CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/vite-env.d.ts1/// <reference types="vite/client" />COMMENT