Repository Analysis

HenryChiao/MIHOMO_YAMLS

一个精心整理的 Mihomo (Clash Meta) 配置文件仓库,通过 GitHub Actions 每日自动同步上游优质规则,提供从入门到进阶的完整解决方案。

92.3 Strong AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of HenryChiao/MIHOMO_YAMLS, a Shell project with 2,348 GitHub stars. SynthScan v2.0 examined 158,555 lines of code across 422 source files, recording 8713 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 92.3 places this repository in the Strong AI signal band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

92.3
Adjusted Score
92.3
Raw Score
100%
Time Factor
2026-07-13
Last Push
2.3K
Stars
Shell
Language
158.6K
Lines of Code
422
Files
8.7K
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 3887LOW 4826

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 8713 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Decorative Section Separators3886 hits · 12200 pts
SeverityFileLineSnippetContext
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml8# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml12# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml15# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml17# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml24# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml26# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml29# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml39# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml41# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml43# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml47# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml49# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml51# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml55# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml57# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml59# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml63# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml65# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml67# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml74# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml76# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml78# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml83# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml107# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml109# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml113# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml311# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml313# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml316# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml446# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml448# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml455# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml477# ==========================================================COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml479# ----------------------------------------------------------COMMENT
MEDIUM…CLASH/Official_Examples/Metacubex/rule-set_config.yaml483# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml8# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml12# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml15# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml17# ----------------------------------------------------------COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml24# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml26# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml29# ----------------------------------------------------------COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml39# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml41# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml43# ----------------------------------------------------------COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml47# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml49# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml51# ----------------------------------------------------------COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml55# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml57# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml59# ----------------------------------------------------------COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml63# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml65# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml67# ----------------------------------------------------------COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml74# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml76# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml78# ----------------------------------------------------------COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml83# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml107# ==========================================================COMMENT
MEDIUM…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml109# ----------------------------------------------------------COMMENT
3826 more matches not shown…
Over-Commented Block4814 hits · 2427 pts
SeverityFileLineSnippetContext
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml1# OpenClash 覆写模块 - rule-set_config.yamlCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml21# +key 数组前置插入:在数组开头插入(规则越靠前越优先匹配)COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml41# ==========================================================COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml61# enable: trueCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml81# 1. 将需要替换的 provider 的 url: 改为你自己的订阅链接COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml101# interval: 86400COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml121# - 台湾COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml141# - name: TelegramCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml161# - 美国COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml181# proxies:COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml201# - 其它地区COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml221# - 默认COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml241# - 全部节点COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml261# - 香港COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml281# - exclude-type: directCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml301# - exclude-type: directCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml321# format: mrsCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml341# type: httpCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml361# github_domain:COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml381# format: mrsCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml401# type: httpCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml421# telegram_ip:COMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml441# format: mrsCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml461# - RULE-SET,youtube_domain,YouTubeCOMMENT
LOW…CLASH/Official_Examples/Metacubex/rule-set_config.yaml481# 如只需修改部分字段,直接写需要修改的键值即可(默认合并,不影响其他字段)。COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml1# OpenClash 覆写模块 - geox_config.yamlCOMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml21# +key 数组前置插入:在数组开头插入(规则越靠前越优先匹配)COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml41# ==========================================================COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml61# enable: trueCOMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml81# 1. 将需要替换的 provider 的 url: 改为你自己的订阅链接COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml101# interval: 86400COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml121# - 台湾COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml141# - name: TelegramCOMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml161# - 美国COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml181# proxies:COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml201# - 其它地区COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml221# - 默认COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml241# - 全部节点COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml261# - 香港COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml281# - exclude-type: directCOMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml301# - exclude-type: directCOMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml321#COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml341COMMENT
LOW…OPENCLASH/Official_Examples/Metacubex/geox_config.yaml361# ipv6: trueCOMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml1# OpenClash 覆写模块 - config.yamlCOMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml21# +key 数组前置插入:在数组开头插入(规则越靠前越优先匹配)COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml41# ==========================================================COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml61# enable: trueCOMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml81# 1. 将需要替换的 provider 的 url: 改为你自己的订阅链接COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml101# client-fingerprint: chromeCOMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml121# override:COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml141# - ALL·延迟最低COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml161# proxies: &id001COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml181# name: 抖音COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml201# type: selectCOMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml221# - filter: ^(?!.*(套餐|重置|剩余|到期|订阅|群|账户|流量|有效期|时间|官网|失联|余额)).*$COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml241# name: NetflixCOMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml261# type: selectCOMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml281# - filter: ^(?!.*(套餐|重置|剩余|到期|订阅|群|账户|流量|有效期|时间|官网|失联|余额)).*$COMMENT
LOW…ite/THENEWOPENCLASH/Mobile_Modules/Surfing/config.yaml301# - icon: https://cdn.jsdelivr.net/gh/GitMetaio/Surfing@main/app/icon/WebRTC.svgCOMMENT
4754 more matches not shown…
Deep Nesting7 hits · 7 pts
SeverityFileLineSnippetContext
LOW.github/scripts/gen_category_docs.py33CODE
LOW.github/scripts/gen_category_docs.py78CODE
LOW.github/scripts/gen_openclash.py99CODE
LOW.github/scripts/gen_openclash.py235CODE
LOW.github/scripts/gen_openclash_new.py225CODE
LOW.github/scripts/analyze_geodata.py28CODE
LOW.github/scripts/analyze_geodata.py89CODE
Excessive Try-Catch Wrapping6 hits · 6 pts
SeverityFileLineSnippetContext
LOW.github/scripts/gen_category_docs.py61 except Exception as e:CODE
MEDIUM.github/scripts/gen_category_docs.py26def get_size(path):CODE
LOW.github/scripts/gen_openclash.py175 except Exception as e:STRING
LOW.github/scripts/gen_openclash.py270 except Exception as e:STRING
LOW.github/scripts/gen_openclash_new.py289 except Exception as e:CODE
LOW.github/scripts/analyze_geodata.py84 except Exception as e:CODE