AI Slop Code Risk Monitor

Open-Dev-Society/OpenStock

Name: Open-Dev-Society/OpenStock — 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).

OpenStock is an open-source alternative to expensive market platforms. Track real-time prices, set personalized alerts, and explore detailed company insights — built openly, for everyone, forever free.

1.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Open-Dev-Society/OpenStock, a TypeScript project with 21,001 GitHub stars. SynthScan examined 33,372 lines of code across 162 source files, recording 36 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 1.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.

1.9

Adjusted Signal

1.9

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

21.0K

Stars

TypeScript

Language

33.4K

Lines of Code

162

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

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

Hallucinated Dependency & Supply Chain Risk 0.6/100 · LOW

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

Agent Over-Engineering Ratio 4.0/100 · LOW

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

PR Review Velocity Impact 7.2/100 · LOW

Which changes need focused human review? 36 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 7LOW 29

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

Decorative Section Separators7 hits · 21 pts

Severity	File	Line	Snippet	Context
MEDIUM	__tests__/ai-provider.test.ts	10	// ── getProviderConfig ──────────────────────────────────────────────	COMMENT
MEDIUM	__tests__/ai-provider.test.ts	71	// ── getFallbackProviderName ────────────────────────────────────────	COMMENT
MEDIUM	__tests__/ai-provider.test.ts	100	// ── callAIProvider ─────────────────────────────────────────────────	COMMENT
MEDIUM	__tests__/ai-provider.test.ts	254	// ── MiniMax request boundary ───────────────────────────────────────	COMMENT
MEDIUM	__tests__/ai-provider.test.ts	318	// ── callAIProviderWithFallback ─────────────────────────────────────	COMMENT
MEDIUM	lib/ai-provider.ts	80	// ── Provider call implementations ──────────────────────────────────	COMMENT
MEDIUM	lib/ai-provider.ts	147	// ── Public API ─────────────────────────────────────────────────────	COMMENT

Verbosity Indicators9 hits · 15 pts

Severity	File	Line	Snippet	Context
LOW	lib/inngest/functions.ts	61	// Step 1: Fetch General Market News	COMMENT
LOW	lib/inngest/functions.ts	88	// Step 3: Send Broadcast via Kit	COMMENT
LOW	lib/inngest/functions.ts	202	// Step 1: Fetch active alerts	COMMENT
LOW⚡	lib/inngest/functions.ts	222	// Step 2: Group by symbol	COMMENT
LOW⚡	lib/inngest/functions.ts	225	// Step 3: Fetch prices	COMMENT
LOW	lib/inngest/functions.ts	244	// Step 4: Check conditions	COMMENT
LOW	lib/inngest/functions.ts	265	// Step 5: Email the alert owner, then mark triggered	COMMENT
LOW	lib/inngest/functions.ts	327	// Step 1: Fetch Inactive Users	COMMENT
LOW	lib/inngest/functions.ts	364	// Step 2: Send Emails	COMMENT

Structural Annotation Overuse9 hits · 15 pts

Severity	File	Line	Snippet	Context
LOW	lib/inngest/functions.ts	61	// Step 1: Fetch General Market News	COMMENT
LOW	lib/inngest/functions.ts	88	// Step 3: Send Broadcast via Kit	COMMENT
LOW	lib/inngest/functions.ts	202	// Step 1: Fetch active alerts	COMMENT
LOW⚡	lib/inngest/functions.ts	222	// Step 2: Group by symbol	COMMENT
LOW⚡	lib/inngest/functions.ts	225	// Step 3: Fetch prices	COMMENT
LOW	lib/inngest/functions.ts	244	// Step 4: Check conditions	COMMENT
LOW	lib/inngest/functions.ts	265	// Step 5: Email the alert owner, then mark triggered	COMMENT
LOW	lib/inngest/functions.ts	327	// Step 1: Fetch Inactive Users	COMMENT
LOW	lib/inngest/functions.ts	364	// Step 2: Send Emails	COMMENT

Hyper-Verbose Identifiers6 hits · 6 pts

Severity	File	Line	Snippet	Context
LOW	scripts/resolve_srv.js	13	async function getStandardConnectionString() {	CODE
LOW	lib/ai-provider.ts	170	export async function callAIProviderWithFallback(	CODE
LOW	lib/utils.ts	240	export function formatSymbolForTradingView(symbol: string): string {	CODE
LOW	lib/actions/adanos.actions.ts	68	export async function getStockSentimentInsights(	CODE
LOW	lib/actions/adanos.helpers.ts	138	export function buildStockSentimentInsights(	CODE
LOW	lib/actions/user.actions.ts	29	export async function getWatchlistSymbolsByEmail(email: string): Promise<string[]> {	CODE

Fake / Example Data4 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	__tests__/welcome-email.test.ts	15	email: 'user@example.com',	CODE
LOW	__tests__/reset-password-email.test.ts	32	email: 'user@example.com',	CODE
LOW	__tests__/reset-password-email.test.ts	48	await sendPasswordResetEmail({ email: 'user@example.com', name: 'User', resetUrl });	CODE
LOW	__tests__/reset-password-email.test.ts	62	email: 'user@example.com',	CODE

Over-Commented Block1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	lib/inngest/functions.ts	441	try {	COMMENT