AI Slop Code Risk Monitor

SoftEtherVPN/SoftEtherVPN

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

Cross-platform multi-protocol VPN software. Pull requests are welcome. The stable version is available at https://github.com/SoftEtherVPN/SoftEtherVPN_Stable.

2.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for SoftEtherVPN/SoftEtherVPN, a C project with 13,695 GitHub stars. SynthScan examined 457,778 lines of code across 459 source files, recording 1297 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 2.1 (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.

2.1
Adjusted Signal
2.1
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
13.7K
Stars
C
Language
457.8K
Lines of Code
459
Files
1.3K
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 10.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 13.2/100 · LOW

Which changes need focused human review? 1297 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 1295

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 1297 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 Block1294 hits · 977 pts
SeverityFileLineSnippetContext
LOWtsan_suppressions.txt21# But if WaitThread reads false, synchronization is ensured by Wait from the PoolWaitList. If it reads true,COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs61COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs81COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs101COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs121COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs141COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs161COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs181COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs201COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs221COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs241COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs261COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs281COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs301COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs321COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs341COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs361COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs381COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs401COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs421COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs441COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs461COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs481COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs501COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs521COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs541COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs561COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs581COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs601COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs621COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs641COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs661COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs681COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs701COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs721COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs741COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs761COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs781COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs801COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs821COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs841COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs861COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs881COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs901COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs921COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs941COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs961COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs981COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1001COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1021COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1041COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1061COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1081COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1101COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1121COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1141COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1161COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1181COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1201COMMENT
LOW…vpnserver-jsonrpc-codegen/VpnServerRpc/VPNServerRpc.cs1221COMMENT
1234 more matches not shown…
Excessive Try-Catch Wrapping2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUM…-iOS/SoftEtherVPN-iOS/Protocol/SoftEtherProtocol.swift76 print("Error sending client signature: \(error)")CODE
MEDIUM…-iOS/SoftEtherVPN-iOS/Protocol/SoftEtherProtocol.swift93 print("Error receiving server response: \(error)")CODE
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWsrc/Mayaqua/Str.c3602Example: "\u006Corem ipsum" -> lorem ipsum */CODE