AI Slop Code Risk Monitor

aldinokemal/go-whatsapp-web-multidevice

SlopCodeMonitor badge for aldinokemal/go-whatsapp-web-multidevice Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

GOWA - WhatsApp REST API with support for UI, Multi Account, Webhooks, and MCP, and Chatwoot. Built with Golang for efficient memory use.

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for aldinokemal/go-whatsapp-web-multidevice, a Go project with 4,986 GitHub stars. SynthScan examined 99,835 lines of code across 382 source files, recording 68 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.7 (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.7
Adjusted Signal
0.7
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
5.0K
Stars
Go
Language
99.8K
Lines of Code
382
Files
68
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 2.2/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.3/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 3.4/100 · LOW

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

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 68 distinct pattern matches across 3 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 Block37 hits · 37 pts
SeverityFileLineSnippetContext
LOWsrc/ui/mcp/route.go21// DeviceMiddleware); a per-call device_id tool argument overrides it (seeCOMMENT
LOWsrc/ui/rest/chatwoot_webhook_auth.go81// chatwootUnsignedWarning logs the explicit open-webhook opt-in once.COMMENT
LOWsrc/ui/rest/chatwoot_webhook_auth.go181}COMMENT
LOWsrc/ui/rest/chatwoot_webhook_auth.go241 return true, nilCOMMENT
LOWsrc/ui/rest/chatwoot.go181// 2. Contact custom attribute gowa_device_id (explicit operator override).COMMENT
LOWsrc/ui/rest/chatwoot_webhook_replay.go61// failure is handled. While a reservation is held, an identical request is notCOMMENT
LOWsrc/domains/chatstorage/interfaces.go61 // GetLatestChatwootMessageLinkByConversation resolves a conversation to itsCOMMENT
LOWsrc/domains/chatstorage/interfaces.go101 ClaimExpiredScheduledSend(now, leaseUntil time.Time, leaseToken string) (*ScheduledSend, error)COMMENT
LOWsrc/config/settings.go101 ChatwootAccountID = 0COMMENT
LOWsrc/config/settings.go121 // the media file (e.g., URL expired). When true, inserts a localizedCOMMENT
LOWsrc/config/settings.go141 // previous open behavior and must be set explicitly.COMMENT
LOWsrc/infrastructure/chatwoot/sync.go781 syncServicesMu sync.RWMutexCOMMENT
LOWsrc/infrastructure/chatwoot/sync.go881}COMMENT
LOWsrc/infrastructure/chatwoot/client.go201 }()COMMENT
LOWsrc/infrastructure/chatwoot/client.go281 resp, err := t.RoundTripper.RoundTrip(req)COMMENT
LOWsrc/infrastructure/chatwoot/client.go741// land in. sourceID is the WhatsApp chat JID, forwarded to CreateConversationCOMMENT
LOWsrc/infrastructure/chatwoot/client.go981 }COMMENT
LOWsrc/infrastructure/chatwoot/url_validation.go81// media and preview fetches: loopback, private, link-local (includingCOMMENT
LOWsrc/infrastructure/chatwoot/pgimport/writer.go21// remaining messages that will all fail.COMMENT
LOWsrc/infrastructure/chatwoot/pgimport/writer.go301// and then re-imported from WhatsApp reuses the same row instead ofCOMMENT
LOWsrc/infrastructure/chatwoot/pgimport/conn.go1// Package pgimport implements the direct-Postgres history importer forCOMMENT
LOWsrc/infrastructure/chatwoot/pgimport/conn.go61 // postgresql://postgres:secret@chatwoot-db:5432/chatwoot_production?sslmode=disableCOMMENT
LOWsrc/infrastructure/whatsapp/history_sync.go421// arrives empty for many of them, and for some it carries the account owner'sCOMMENT
LOWsrc/infrastructure/whatsapp/own_sender.go1package whatsappCOMMENT
LOWsrc/infrastructure/whatsapp/event_message.go181 }COMMENT
LOWsrc/infrastructure/whatsapp/event_message.go521 // media on *every* card: reusing those fields would have each card'sCOMMENT
LOWsrc/infrastructure/whatsapp/database.go241// checks. A non-empty first value is preserved, including disable, require,COMMENT
LOWsrc/infrastructure/whatsapp/reachout_error.go1package whatsappCOMMENT
LOWsrc/infrastructure/whatsapp/webhook_forward.go41 // 1:1 JID from the WhatsApp contact store. It is a seam so tests can stubCOMMENT
LOWsrc/usecase/message.go421COMMENT
LOWsrc/usecase/schedule.go441 if err := s.processJob(ctx, job); err != nil {COMMENT
LOWsrc/pkg/utils/chatwoot.go61// IsNewsletterJID reports whether jid belongs to a WhatsApp channelCOMMENT
LOWsrc/pkg/utils/chatwoot.go81// The transforms use paired, non-greedy delimiters, so a lone unmatchedCOMMENT
LOWsrc/pkg/utils/chatwoot.go101// <https://x.example/> -> https://x.example/COMMENT
LOWsrc/pkg/utils/chatwoot.go121 // lazy ("??") so the pair closes at the first run that can close it.COMMENT
LOWsrc/pkg/utils/image_bounds.go21 MaxImageEdge = 32768COMMENT
LOWsrc/pkg/utils/business_message.go381 lines = append(lines, value)COMMENT
Fake / Example Data27 hits · 26 pts
SeverityFileLineSnippetContext
LOWdocs/webhook-payload.md251 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md270 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md291 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1246 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1263 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1284 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1305 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1326 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1343 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1364 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1385 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1402 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1423 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1446 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1561 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1583 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1645 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1667 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1694 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1715 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1735 "from_name": "John Doe",CODE
LOWdocs/webhook-payload.md1755 "from_name": "John Doe",CODE
LOWdocs/openapi.yaml1183 example: 'John Doe'CODE
LOWdocs/openapi.yaml5669 example: 'John Doe'CODE
LOWdocs/openapi.yaml5791 example: 'John Doe'CODE
LOWdocs/openapi.yaml6337 example: "John Doe"CODE
LOWdocs/openapi.yaml6475 example: 'John Doe'CODE
Structural Annotation Overuse4 hits · 8 pts
SeverityFileLineSnippetContext
LOWdocs/chatwoot.md135### Step 1: Create an API Channel InboxCOMMENT
LOW⚡docs/chatwoot.md147### Step 2: Get Your API TokenCOMMENT
LOW⚡docs/chatwoot.md153### Step 3: Find Your Account IDCOMMENT
LOW⚡docs/chatwoot.md160### Step 4: Configure the API Channel WebhookCOMMENT