AI Slop Code Risk Monitor

infinitered/reactotron

Name: infinitered/reactotron — TypeScript Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A desktop app for inspecting your React JS and React Native projects. macOS, Linux, and Windows.

0.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for infinitered/reactotron, a TypeScript project with 15,595 GitHub stars. SynthScan examined 39,155 lines of code across 515 source files, recording 26 pattern matches distributed across 6 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-08-13

Last Push

15.6K

Stars

TypeScript

Language

39.2K

Lines of Code

515

Files

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 4.1/100 · LOW

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

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

PR Review Velocity Impact 3.5/100 · LOW

Which changes need focused human review? 26 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 1LOW 25

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 26 distinct pattern matches across 6 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.

Over-Commented Block10 hits · 10 pts

Severity	File	Line	Snippet	Context
LOW	scripts/git-clone-fork-to-trusted-branch.sh	1	#!/bin/bash	COMMENT
LOW	lib/reactotron-react-native/src/plugins/asyncStorage.ts	121	// eslint-disable-next-line @typescript-eslint/ban-ts-comment	COMMENT
LOW	lib/reactotron-react-native/src/plugins/asyncStorage.ts	161	reactotron.asyncStorageHandler.setItem = swizzSetItem	COMMENT
LOW	lib/reactotron-core-client/README.md	501	// This is an object (not a function). The keys are strings. The values are functions.	COMMENT
LOW	lib/reactotron-core-client/test/stopwatch.test.ts	21	// // here's a callback version	COMMENT
LOW	lib/reactotron-core-client/src/plugins/repl.ts	21	// reactotron.send("repl.cd.response", "That REPL does not exist")	COMMENT
LOW	.circleci/config.yml	401	# - reactotron-npm-context	COMMENT
LOW	…otron-app/src/renderer/pages/reactNative/Storybook.tsx	81	text: "Storybook",	COMMENT
LOW	…otron-app/src/renderer/pages/reactNative/Storybook.tsx	101	// },	COMMENT
LOW	apps/example-app/app/utils/crashReporting.ts	61	// Sentry.captureException(error)	COMMENT

Hyper-Verbose Identifiers10 hits · 10 pts

Severity	File	Line	Snippet	Context
LOW	…eactotron-react-native/src/plugins/storybook/index.tsx	24	function StorybookSwitcherContainer(props: any) {	CODE
LOW	…native/src/helpers/getReactNativeVersionWithModules.ts	1	export function getReactNativeVersionWithModules(constants: any): string \| null {	CODE
LOW	…/src/helpers/getReactNativeDimensionsWithDimensions.ts	12	export function getReactNativeDimensionsWithDimensions(	CODE
LOW	…-native/src/helpers/getReactNativePlatformConstants.ts	14	export default function getReactNativePlatformConstants(): PlatformConstants {	CODE
LOW	lib/reactotron-mst/src/reactotron-mst.ts	214	function attachReactotronToMstNode(node: IStateTreeNode, nodeName?: string) {	CODE
LOW	lib/reactotron-mcp/src/redaction.ts	209	function compileCombinedValueRegex(patterns: string[]): RegExp \| null {	CODE
LOW	lib/reactotron-mcp/src/redaction.ts	437	function redactAsyncStorageWithParsed(data: unknown, parsed: ParsedRules): unknown {	CODE
LOW	lib/reactotron-redux/src/subscriptionsHandler.ts	3	export default function createSubscriptionHandler(	CODE
LOW	lib/reactotron-redux/src/subscriptionsHandler.ts	59	function sendSubscriptionsIfNeeded() {	CODE
LOW	apps/example-app/app/navigators/navigationUtilities.ts	96	function navigationRestoredDefaultState(persistNavigation: PersistNavigationConfig) {	CODE

Structural Annotation Overuse3 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW⚡	docs/contributing/index.md	11	### Step 1: Get the development version of reactotron running	COMMENT
LOW⚡	docs/contributing/index.md	19	### Step 2: Use the example react-native app to test your changes	COMMENT
LOW⚡	docs/contributing/index.md	25	### Step 3: Making changes	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	apps/example-app/app/utils/crashReporting.ts	59	// In production, utilize crash reporting service of choice below:	COMMENT

Redundant / Tautological Comments1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	scripts/git-clone-fork-to-trusted-branch.sh	32	# Check if 'fork-to-test' remote exists and then remove it	COMMENT

Verbosity Indicators1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	lib/reactotron-react-native/src/plugins/devTools.ts	41	// the DevMenu module is not available in all environments, like Expo Go, so we need to check if it exists	COMMENT