AI Slop Code Risk Monitor

reactjs/react.dev

SlopCodeMonitor badge for reactjs/react.dev Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

The React documentation website

0.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for reactjs/react.dev, a JavaScript project with 11,827 GitHub stars. SynthScan examined 184,227 lines of code across 430 source files, recording 87 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.8 (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.8
Adjusted Signal
0.8
Raw Pattern Score
100%
Time Factor
2026-10-27
Last Push
11.8K
Stars
JavaScript
Language
184.2K
Lines of Code
430
Files
87
Pattern Hits
2026-10-31
Scan Date
0.01
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.8/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 87 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 0.8/100 · LOW

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

PR Review Velocity Impact 3.0/100 · LOW

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

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

Structural Annotation Overuse50 hits · 77 pts
SeverityFileLineSnippetContext
LOW.claude/skills/write/SKILL.md42### Step 1: Parse IntentCOMMENT
LOW.claude/skills/write/SKILL.md55### Step 2: Research (Parallel Agents)COMMENT
LOW.claude/skills/write/SKILL.md104### Step 3: Synthesize Writing PlanCOMMENT
LOW.claude/skills/write/SKILL.md120### Step 4: Write DocumentationCOMMENT
LOW.claude/skills/write/SKILL.md154### Step 5: Review DocumentationCOMMENT
LOW.claude/skills/write/SKILL.md162### Step 6: Fix IssuesCOMMENT
LOW.claude/skills/docs-writer-learn/SKILL.md200### Step 1: Action to take {/*step-1-action*/}COMMENT
LOW.claude/skills/docs-writer-learn/SKILL.md201### Step 2: Next action {/*step-2-next-action*/}COMMENT
LOW.claude/skills/react-expert/SKILL.md45### Step 1: Setup React RepoCOMMENT
LOW.claude/skills/react-expert/SKILL.md63### Step 2: Dispatch 6 Parallel Research AgentsCOMMENT
LOW.claude/skills/react-expert/SKILL.md78### Step 3: Agent PromptsCOMMENT
LOW.claude/skills/react-expert/SKILL.md237### Step 4: Synthesize ResultsCOMMENT
LOW.claude/skills/react-expert/SKILL.md243### Step 5: Save OutputCOMMENT
LOWsrc/content/learn/passing-props-to-a-component.md70### Step 1: Pass props to the child component {/*step-1-pass-props-to-the-child-component*/}COMMENT
LOWsrc/content/learn/passing-props-to-a-component.md93### Step 2: Read props inside the child component {/*step-2-read-props-inside-the-child-component*/}COMMENT
LOW…content/learn/extracting-state-logic-into-a-reducer.md190### Step 1: Move from setting state to dispatching actions {/*step-1-move-from-setting-state-to-dispatching-actions*/}COMMENT
LOW…content/learn/extracting-state-logic-into-a-reducer.md287### Step 2: Write a reducer function {/*step-2-write-a-reducer-function*/}COMMENT
LOW…content/learn/extracting-state-logic-into-a-reducer.md460### Step 3: Use the reducer from your component {/*step-3-use-the-reducer-from-your-component*/}COMMENT
LOWsrc/content/learn/sharing-state-between-components.md104### Step 1: Remove state from the child components {/*step-1-remove-state-from-the-child-components*/}COMMENT
LOWsrc/content/learn/sharing-state-between-components.md120### Step 2: Pass hardcoded data from the common parent {/*step-2-pass-hardcoded-data-from-the-common-parent*/}COMMENT
LOWsrc/content/learn/sharing-state-between-components.md177### Step 3: Add state to the common parent {/*step-3-add-state-to-the-common-parent*/}COMMENT
LOWsrc/content/learn/synchronizing-with-effects.md54### Step 1: Declare an Effect {/*step-1-declare-an-effect*/}COMMENT
LOWsrc/content/learn/synchronizing-with-effects.md229### Step 2: Specify the Effect dependencies {/*step-2-specify-the-effect-dependencies*/}COMMENT
LOWsrc/content/learn/synchronizing-with-effects.md464### Step 3: Add cleanup if needed {/*step-3-add-cleanup-if-needed*/}COMMENT
LOW⚡src/content/learn/your-first-component.md81### Step 1: Export the component {/*step-1-export-the-component*/}COMMENT
LOW⚡src/content/learn/your-first-component.md85### Step 2: Define the function {/*step-2-define-the-function*/}COMMENT
LOW⚡src/content/learn/your-first-component.md95### Step 3: Add markup {/*step-3-add-markup*/}COMMENT
LOWsrc/content/learn/passing-data-deeply-with-context.md229### Step 1: Create the context {/*step-1-create-the-context*/}COMMENT
LOWsrc/content/learn/passing-data-deeply-with-context.md313### Step 2: Use the context {/*step-2-use-the-context*/}COMMENT
LOWsrc/content/learn/passing-data-deeply-with-context.md449### Step 3: Provide the context {/*step-3-provide-the-context*/}COMMENT
LOW…c/content/learn/scaling-up-with-reducer-and-context.md242### Step 1: Create the context {/*step-1-create-the-context*/}COMMENT
LOW…c/content/learn/scaling-up-with-reducer-and-context.md453### Step 2: Put state and dispatch into context {/*step-2-put-state-and-dispatch-into-context*/}COMMENT
LOW…c/content/learn/scaling-up-with-reducer-and-context.md674### Step 3: Use context anywhere in the tree {/*step-3-use-context-anywhere-in-the-tree*/}COMMENT
LOWsrc/content/learn/build-a-react-app-from-scratch.md28## Step 1: Install a build tool {/*step-1-install-a-build-tool*/}COMMENT
LOWsrc/content/learn/build-a-react-app-from-scratch.md72## Step 2: Build Common Application Patterns {/*step-2-build-common-application-patterns*/}COMMENT
LOWsrc/content/learn/thinking-in-react.md34## Step 1: Break the UI into a component hierarchy {/*step-1-break-the-ui-into-a-component-hierarchy*/}COMMENT
LOWsrc/content/learn/thinking-in-react.md74## Step 2: Build a static version in React {/*step-2-build-a-static-version-in-react*/}COMMENT
LOWsrc/content/learn/thinking-in-react.md208## Step 3: Find the minimal but complete representation of UI state {/*step-3-find-the-minimal-but-complete-representatiCOMMENT
LOWsrc/content/learn/thinking-in-react.md251## Step 4: Identify where your state should live {/*step-4-identify-where-your-state-should-live*/}COMMENT
LOWsrc/content/learn/thinking-in-react.md463## Step 5: Add inverse data flow {/*step-5-add-inverse-data-flow*/}COMMENT
LOWsrc/content/learn/add-react-to-an-existing-project.md42### Step 1: Set up a modular JavaScript environment {/*step-1-set-up-a-modular-javascript-environment*/}COMMENT
LOWsrc/content/learn/add-react-to-an-existing-project.md92### Step 2: Render React components anywhere on the page {/*step-2-render-react-components-anywhere-on-the-page*/}COMMENT
LOWsrc/content/learn/render-and-commit.md32## Step 1: Trigger a render {/*step-1-trigger-a-render*/}COMMENT
LOWsrc/content/learn/render-and-commit.md78## Step 2: React renders your components {/*step-2-react-renders-your-components*/}COMMENT
LOWsrc/content/learn/render-and-commit.md149## Step 3: React commits changes to the DOM {/*step-3-react-commits-changes-to-the-dom*/}COMMENT
LOWsrc/content/learn/reacting-to-input-with-state.md152### Step 1: Identify your component's different visual states {/*step-1-identify-your-components-different-visual-statesCOMMENT
LOWsrc/content/learn/reacting-to-input-with-state.md314### Step 2: Determine what triggers those state changes {/*step-2-determine-what-triggers-those-state-changes*/}COMMENT
LOWsrc/content/learn/reacting-to-input-with-state.md351### Step 3: Represent the state in memory with `useState` {/*step-3-represent-the-state-in-memory-with-usestate*/}COMMENT
LOWsrc/content/learn/reacting-to-input-with-state.md376### Step 4: Remove any non-essential state variables {/*step-4-remove-any-non-essential-state-variables*/}COMMENT
LOWsrc/content/learn/reacting-to-input-with-state.md404### Step 5: Connect the event handlers to set state {/*step-5-connect-the-event-handlers-to-set-state*/}COMMENT
AI Response Leakage5 hits · 35 pts
SeverityFileLineSnippetContext
HIGH.claude/skills/docs-writer-reference/SKILL.md580### I've updated the state, but logging gives me the old value {/*old-value*/}COMMENT
HIGHsrc/content/learn/removing-effect-dependencies.md554The final code is longer than the original, but splitting these Effects is still correct. [Each Effect should represent CODE
HIGHsrc/content/reference/react-dom/client/createRoot.md479### I've created a root, but nothing is displayed {/*ive-created-a-root-but-nothing-is-displayed*/}COMMENT
HIGHsrc/content/reference/react/useState.md1151### I've updated the state, but logging gives me the old value {/*ive-updated-the-state-but-logging-gives-me-the-old-valCOMMENT
HIGHsrc/content/reference/react/useState.md1182### I've updated the state, but the screen doesn't update {/*ive-updated-the-state-but-the-screen-doesnt-update*/}COMMENT
Hyper-Verbose Identifiers29 hits · 29 pts
SeverityFileLineSnippetContext
LOWeslint-local-rules/rules/metadata.js77function parseExpectedErrorsEntries(rawEntries) {CODE
LOWeslint-local-rules/rules/metadata.js222function metadataHasExpectedErrorsToken(metadata) {CODE
LOWeslint-local-rules/rules/metadata.js226function stringifyExpectedErrorsToken(token) {CODE
LOWeslint-local-rules/rules/metadata.js346function removeCompilerExpectedLines(metadata) {CODE
LOWscripts/deadLinkChecker.js53function extractAnchorsFromContent(content) {CODE
LOWsrc/content/learn/removing-effect-dependencies.md1887export function createEncryptedConnection({ serverUrl, roomId }) {CODE
LOWsrc/content/learn/removing-effect-dependencies.md1928export function createUnencryptedConnection({ serverUrl, roomId }) {CODE
LOWsrc/content/learn/removing-effect-dependencies.md2187export function createEncryptedConnection({ serverUrl, roomId }) {CODE
LOWsrc/content/learn/removing-effect-dependencies.md2228export function createUnencryptedConnection({ serverUrl, roomId }) {CODE
LOWsrc/content/learn/lifecycle-of-reactive-effects.md1393export function createEncryptedConnection(roomId) {CODE
LOWsrc/content/learn/lifecycle-of-reactive-effects.md1405export function createUnencryptedConnection(roomId) {CODE
LOWsrc/content/learn/lifecycle-of-reactive-effects.md1490export function createEncryptedConnection(roomId) {CODE
LOWsrc/content/learn/lifecycle-of-reactive-effects.md1502export function createUnencryptedConnection(roomId) {CODE
LOWsrc/content/learn/lifecycle-of-reactive-effects.md1585export function createEncryptedConnection(roomId) {CODE
LOWsrc/content/learn/lifecycle-of-reactive-effects.md1597export function createUnencryptedConnection(roomId) {CODE
LOWsrc/content/learn/react-compiler/introduction.md131function expensivelyProcessAReallyLargeArrayOfObjects() { /* ... */ }CODE
LOWsrc/content/blog/2022/03/08/react-18-upgrade-guide.md87function AppWithCallbackAfterRender() {CODE
LOWsrc/content/blog/2026/09/09/react-19-3.md1612export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/content/blog/2026/09/09/react-19-3.md1752export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/content/reference/react-dom/browser.md150export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/content/reference/react-dom/browser.md317export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/content/reference/react-dom/server/resume.md202export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/content/reference/react/use.md1422export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/content/reference/react/Suspense.md472export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/content/reference/react/Suspense.md2476export async function flushReadableStreamToFrame(readable, frame) {CODE
LOWsrc/utils/prepareMDX.js27function wrapChildrenInMaxWidthContainers(children) {CODE
LOWsrc/components/Search.tsx49function useDocSearchKeyboardEvents({CODE
LOW…X/Sandpack/sandpack-rsc/sandbox-code/src/rsc-server.js78function transformInlineServerActions(code) {CODE
LOWsrc/components/Layout/useTocHighlight.tsx62 function throttledUpdateActiveLink() {CODE
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWnext-env.d.ts1/// <reference types="next" />COMMENT
LOW.github/workflows/analyze.yml61 if: success() && github.event.numberCOMMENT
LOWsrc/components/MDX/Sandpack/Preview.tsx141 };COMMENT