AI Slop Code Risk Monitor

infinitered/ignite

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

Infinite Red's battle-tested React Native project boilerplate, along with a CLI, component/model generators, and more! 9 years of continuous development and counting.

0.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for infinitered/ignite, a TypeScript project with 19,949 GitHub stars. SynthScan examined 35,060 lines of code across 259 source files, recording 26 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.9 (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.9
Adjusted Signal
0.9
Raw Pattern Score
100%
Time Factor
2026-06-07
Last Push
19.9K
Stars
TypeScript
Language
35.1K
Lines of Code
259
Files
26
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.5/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.0/100 · LOW

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

Agent Over-Engineering Ratio 2.4/100 · LOW

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

PR Review Velocity Impact 4.2/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 2LOW 24

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 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 Identifiers15 hits · 17 pts
SeverityFileLineSnippetContext
LOWtest/_test-helpers.ts144export async function spawnIgniteAndPrintIfFail(CODE
LOW⚡test/_test-helpers.ts157function generateScreenTemplatePath(pathname: string): string {CODE
LOW⚡test/_test-helpers.ts161function generateRouteTemplatePath(pathname: string): string {CODE
LOW⚡test/_test-helpers.ts165function generateDynamicRouteTemplatePath(pathname: string): string {CODE
LOW⚡test/_test-helpers.ts169export function copyDefaultScreenGenerator(tempBoilerplatePath: string): void {CODE
LOWtest/_test-helpers.ts180export function copyExpoRouterGeneratorTemplates(tempBoilerplatePath: string): void {CODE
LOWtest/_test-helpers.ts196export function removeExpoRouterGeneratorTemplates(tempBoilerplatePath: string): void {CODE
LOWtest/vanilla/ignite-new.test.ts318async function checkForLeftoverHelloWorld(filePath: string) {CODE
LOWboilerplate/app/navigators/navigationUtilities.ts103function navigationRestoredDefaultState(persistNavigation: PersistNavigationConfig) {CODE
LOWsrc/tools/react-native.ts300export function refactorExpoRouterReactotronCmds(toolbox: GluegunToolbox) {CODE
LOWsrc/tools/react-native.ts361export function updateExpoRouterPackageJson(toolbox: GluegunToolbox) {CODE
LOWsrc/tools/react-native.ts395export function cleanupExpoRouterConversion(toolbox: GluegunToolbox, targetPath: string) {CODE
LOWsrc/tools/react-native.ts410export function updatePackagerCommandsInReadme(readmePath: string, packagerName: PackagerName) {CODE
LOWsrc/tools/generators.ts767export async function validateSplashScreenGenerator(CODE
LOWsrc/commands/new.ts1066export function findAndRemoveDependencies(CODE
Fake / Example Data7 hits · 7 pts
SeverityFileLineSnippetContext
LOWdocs/boilerplate/app/components/TextField.md25 placeholder="John Doe"CODE
LOW…app/screens/DemoShowroomScreen/demos/DemoTextField.tsx61 placeholderTxOptions={{ prop: "placeholder" }}CODE
LOW…app/screens/DemoShowroomScreen/demos/DemoTextField.tsx74 placeholderTxOptions={{ prop: "placeholder" }}CODE
LOW…app/screens/DemoShowroomScreen/demos/DemoTextField.tsx87 placeholderTxOptions={{ prop: "placeholder" }}CODE
LOW…app/screens/DemoShowroomScreen/demos/DemoTextField.tsx101 placeholderTxOptions={{ prop: "placeholder" }}CODE
LOW…app/screens/DemoShowroomScreen/demos/DemoTextField.tsx112 placeholderTxOptions={{ prop: "placeholder" }}CODE
LOWboilerplate/app/i18n/demo-ar.ts55 placeholder: "عبر 'placeholder' الدعامة",CODE
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMboilerplate/app/utils/crashReporting.ts56 // In production, utilize crash reporting service of choice below:COMMENT
MEDIUMsrc/commands/new.ts673 // use-cache defaults to `false` for now; if we make it robust enough,COMMENT
Over-Commented Block2 hits · 2 pts
SeverityFileLineSnippetContext
LOWboilerplate/app/utils/gestureHandler.ts1// Don't import react-native-gesture-handler on webCOMMENT
LOWboilerplate/.maestro/shared/_OnFlowStart.yaml1# flow: Shared _OnFlowStartCOMMENT