AI Slop Code Risk Monitor

virattt/dexter

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

An autonomous agent for deep financial research

3.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for virattt/dexter, a TypeScript project with 27,736 GitHub stars. SynthScan examined 41,454 lines of code across 235 source files, recording 73 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 3.2 (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.

3.2
Adjusted Signal
3.2
Raw Pattern Score
100%
Time Factor
2026-09-23
Last Push
27.7K
Stars
TypeScript
Language
41.5K
Lines of Code
235
Files
73
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 8.7/100 · LOW

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

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

PR Review Velocity Impact 12.5/100 · LOW

Which changes need focused human review? 73 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 19LOW 54

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

Decorative Section Separators19 hits · 57 pts
SeverityFileLineSnippetContext
MEDIUMsrc/tools/search/x-search.ts209// ─── Tool definition ─────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts33// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts35// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts104// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts106// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts152// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts154// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts180// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/permissions/rules.ts182// ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts48 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts50 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts118 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts120 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts183 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts185 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts231 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts233 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts260 // ──────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMsrc/components/question-prompt.ts262 // ──────────────────────────────────────────────────────────────────────────COMMENT
Structural Annotation Overuse24 hits · 39 pts
SeverityFileLineSnippetContext
LOWsrc/tools/finance/read-filings.ts173 // Step 1: Plan ticker + filing types using structured outputCOMMENT
LOWsrc/tools/finance/read-filings.ts246 // Step 2: Select and read filing content with canonical item namesCOMMENT
LOWsrc/tools/finance/screen-stocks.ts123 // Step 1: Fetch screener metrics (cached after first call)COMMENT
LOWsrc/tools/finance/screen-stocks.ts138 // Step 2: LLM structured output — translate natural language → filtersCOMMENT
LOWsrc/tools/finance/screen-stocks.ts158 // Step 3: POST to screener APICOMMENT
LOWsrc/agent/agent.ts575 // Step 1: Memory flushCOMMENT
LOWsrc/agent/agent.ts601 // Step 2: CompactionCOMMENT
LOWsrc/agent/agent.ts654 // Step 3: Fallback — truncate oldest roundsCOMMENT
LOWsrc/skills/write-memo/SKILL.md25## Step 1: Frame the TradeCOMMENT
LOWsrc/skills/write-memo/SKILL.md37## Step 2: Gather Data (Parallel)COMMENT
LOWsrc/skills/write-memo/SKILL.md72## Step 3: Build ScenariosCOMMENT
LOWsrc/skills/write-memo/SKILL.md90## Step 4: Optional DCF AnchorCOMMENT
LOWsrc/skills/write-memo/SKILL.md94## Step 5: Draft Memo ContentCOMMENT
LOWsrc/skills/write-memo/SKILL.md142## Step 6: Self-Critique Pass (Mandatory)COMMENT
LOWsrc/skills/write-memo/SKILL.md154## Step 7: Render HTMLCOMMENT
LOWsrc/skills/write-memo/SKILL.md167## Step 8: Report to ChatCOMMENT
LOWsrc/skills/dcf/SKILL.md23## Step 1: Gather Financial DataCOMMENT
LOWsrc/skills/dcf/SKILL.md62## Step 2: Calculate FCF Growth RateCOMMENT
LOWsrc/skills/dcf/SKILL.md72## Step 3: Estimate Discount Rate (WACC)COMMENT
LOW⚡src/skills/dcf/SKILL.md87## Step 4: Project Future Cash FlowsCOMMENT
LOW⚡src/skills/dcf/SKILL.md93## Step 5: Calculate Present ValueCOMMENT
LOW⚡src/skills/dcf/SKILL.md97## Step 6: Sensitivity AnalysisCOMMENT
LOW⚡src/skills/dcf/SKILL.md101## Step 7: Validate ResultsCOMMENT
LOWsrc/skills/dcf/SKILL.md116## Step 8: Output FormatCOMMENT
Hyper-Verbose Identifiers22 hits · 24 pts
SeverityFileLineSnippetContext
LOWsrc/tools/registry.ts263export function buildCompactToolDescriptions(model: string): string {CODE
LOWsrc/tools/fetch/utils.ts153export async function getWithPermittedRedirects(CODE
LOWsrc/tools/finance/formatters.ts148export function formatHistoricalKeyRatios(data: unknown, args?: Rec): string {CODE
LOWsrc/tools/finance/formatters.ts251export function formatBeneficialOwnership(data: unknown): string {CODE
LOWsrc/tools/finance/formatters.ts264export function formatInstitutionalHoldings(data: unknown, args?: Rec): string {CODE
LOWsrc/memory/temporal-decay.ts28export function calculateTemporalDecayMultiplier(params: {CODE
LOWsrc/utils/model.ts52export function getDefaultModelForProvider(providerId: string): string | undefined {CODE
LOWsrc/utils/tokens.ts39export function getEffectiveContextWindow(model: string): number {CODE
LOWsrc/utils/env.ts16export function checkApiKeyExistsForProvider(providerId: string): boolean {CODE
LOW⚡src/utils/env.ts112export function getSearchProviderDisplayName(providerId: SearchProviderId): string {CODE
LOW⚡src/utils/env.ts116export function getApiKeyNameForSearchProvider(providerId: SearchProviderId): string {CODE
LOW⚡src/utils/env.ts120export function checkApiKeyForSearchProvider(providerId: SearchProviderId): boolean {CODE
LOW⚡src/utils/env.ts124export function saveApiKeyForSearchProvider(providerId: SearchProviderId, apiKey: string): boolean {CODE
LOWsrc/agent/compact.ts154export function buildCompactSummaryMessage(summary: string): string {CODE
LOWsrc/components/select-list.ts57export function createSearchProviderSelector(CODE
LOWsrc/components/select-list.ts117export function createApiKeyConfirmSelector(onConfirm: (wantsToSet: boolean) => void) {CODE
LOWsrc/model/llm.ts281function annotateSystemMessageForCaching(messages: BaseMessage[]): BaseMessage[] {CODE
LOWsrc/skills/registry.ts107export function buildSkillMetadataSection(): string {CODE
LOWsrc/gateway/access-control.ts95export async function checkInboundAccessControl(params: {CODE
LOWsrc/gateway/group/history-buffer.ts44export function getAndClearGroupHistory(groupId: string): GroupHistoryEntry[] {CODE
LOWsrc/gateway/group/history-buffer.ts54export function formatGroupHistoryContext(params: {CODE
LOWsrc/gateway/channels/whatsapp/auth-store.ts40export function maybeRestoreCredsFromBackup(authDir: string): void {CODE
Verbosity Indicators8 hits · 12 pts
SeverityFileLineSnippetContext
LOWsrc/tools/finance/read-filings.ts173 // Step 1: Plan ticker + filing types using structured outputCOMMENT
LOWsrc/tools/finance/read-filings.ts246 // Step 2: Select and read filing content with canonical item namesCOMMENT
LOWsrc/tools/finance/screen-stocks.ts123 // Step 1: Fetch screener metrics (cached after first call)COMMENT
LOWsrc/tools/finance/screen-stocks.ts138 // Step 2: LLM structured output — translate natural language → filtersCOMMENT
LOWsrc/tools/finance/screen-stocks.ts158 // Step 3: POST to screener APICOMMENT
LOWsrc/agent/agent.ts575 // Step 1: Memory flushCOMMENT
LOWsrc/agent/agent.ts601 // Step 2: CompactionCOMMENT
LOWsrc/agent/agent.ts654 // Step 3: Fallback — truncate oldest roundsCOMMENT