AI Slop Code Risk Monitor

ACL4SSR/ACL4SSR

Name: ACL4SSR/ACL4SSR — Python 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).

SSR 去广告ACL规则/SS完整GFWList规则/Clash规则碎片，Telegram频道订阅地址

0.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for ACL4SSR/ACL4SSR, a Python project with 6,886 GitHub stars. SynthScan examined 38,995 lines of code across 187 source files, recording 35 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-10-31

Last Push

6.9K

Stars

Python

Language

39.0K

Lines of Code

187

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

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

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

PR Review Velocity Impact 4.6/100 · LOW

Which changes need focused human review? 35 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 1LOW 34

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

Over-Commented Block20 hits · 20 pts

Severity	File	Line	Snippet	Context
LOW	Clash/GeneralClashConfig.yml	1	#---------------------------------------------------#	COMMENT
LOW	Clash/GeneralClashConfig.yml	21	# #"*": 绑定所有IP地址	COMMENT
LOW	Clash/GeneralClashConfig.yml	41	# yacd面板： https://github.com/haishanh/yacd	COMMENT
LOW	Clash/GeneralClashConfig.yml	61	#hosts:	COMMENT
LOW	Clash/GeneralClashConfig.yml	81	#- https://dns.alidns.com/dns-query # 阿里 DoH DNS	COMMENT
LOW	Clash/GeneralClashConfig.yml	101	#	COMMENT
LOW	Clash/GeneralClashConfig.yml	121	# server: 127.0.0.1	COMMENT
LOW	Clash/GeneralClashConfig.yml	141	#listen: :53	COMMENT
LOW	Clash/GeneralClashConfig.yml	161	cfw-conn-break-strategy:	COMMENT
LOW	Clash/GeneralClashConfig.yml	181	# default：按配置文件定义节点顺序	COMMENT
LOW	Clash/GeneralClashConfig.yml	201	#windowsHide: true # 隐藏子进程的控制台窗口	COMMENT
LOW	Clash/Providers/ProxyMedia.yaml	501	# YouTubeMusic	COMMENT
LOW	Clash/Providers/Download.yaml	1	payload:	COMMENT
LOW	Clash/Providers/Download.yaml	21	# URL-REGEX,(.?)(xunlei\|sandai\|Thunder\|XLLiveUD)(.)	COMMENT
LOW	Clash/Providers/Ruleset/Pandora.yaml	1	payload:	COMMENT
LOW	Clash/Providers/Ruleset/Download.yaml	1	payload:	COMMENT
LOW	Clash/Providers/Ruleset/Download.yaml	21	# URL-REGEX,(.+\.\|^)(360\|so)\.(cn\|com)	COMMENT
LOW	Clash/Providers/Ruleset/RemoteDesktop.yaml	1	payload:	COMMENT
LOW	Clash/Providers/Ruleset/AppleNews.yaml	1	payload:	COMMENT
LOW	Clash/Providers/Ruleset/YouTubeMusic.yaml	1	payload:	COMMENT

Excessive Try-Catch Wrapping4 hits · 5 pts

Severity	File	Line	Snippet	Context
LOW	scripts/gfwlist_parser.py	83	except Exception as e:	CODE
MEDIUM	scripts/gfwlist_parser.py	84	print(f"Error fetching GFWList: {e}")	CODE
LOW	scripts/gfwlist_parser.py	260	except Exception as e:	CODE
LOW	scripts/gfwlist_parser.py	293	except Exception as e:	CODE

Hyper-Verbose Identifiers6 hits · 5 pts

Severity	File	Line	Snippet	Context
LOW	scripts/gfwlist_parser.py	154	def format_domain_suffix_rules(domains):	CODE
LOW	scripts/gfwlist_parser.py	229	def split_existing_rule_files():	CODE
LOW	scripts/gfwlist_parser.py	339	def generate_clash_provider_yaml(domain_list, ip_list, filename, title="payload"):	STRING
LOW	scripts/gfwlist_parser.py	367	def generate_clash_ruleset_list(domain_list, ip_list, filename, title="GFWList"):	STRING
LOW	scripts/tests/test_mrs_domain_patterns.py	15	def test_generated_clash_rules_are_preserved_and_mrs_inputs_are_patterns(self):	CODE
LOW	scripts/tests/test_mrs_domain_patterns.py	48	def test_exact_and_suffix_rule_mappings(self):	CODE

Deep Nesting5 hits · 5 pts

Severity	File	Line	Context
LOW	scripts/gfwlist_parser.py	30	CODE
LOW	scripts/gfwlist_parser.py	100	CODE
LOW	scripts/gfwlist_parser.py	247	CODE
LOW	scripts/gfwlist_parser.py	280	CODE
LOW	scripts/gfwlist_parser.py	396	CODE