AI Slop Code Risk Monitor

XTLS/Xray-core

Name: XTLS/Xray-core — Go 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).

Xray, Penetrates Everything. Also the best v2ray-core. Where the magic happens. An open platform for various uses.

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for XTLS/Xray-core, a Go project with 42,505 GitHub stars. SynthScan examined 196,124 lines of code across 1080 source files, recording 43 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.3 (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.3

Adjusted Signal

0.3

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

42.5K

Stars

Language

196.1K

Lines of Code

1.1K

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

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

Hallucinated Dependency & Supply Chain Risk 0.6/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 1.5/100 · LOW

Which changes need focused human review? 43 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 2HIGH 0MEDIUM 0LOW 41

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 43 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 Block35 hits · 35 pts

Severity	File	Line	Snippet	Context
LOW	…rt/internet/hysteria/congestion/bbr/windowed_filter.go	1	package bbr	COMMENT
LOW	…rt/internet/hysteria/congestion/bbr/windowed_filter.go	21	// (or higher) than everything else in the window and it is the most recent.	COMMENT
LOW	…/internet/hysteria/congestion/bbr/bandwidth_sampler.go	21	type sendTimeState struct {	COMMENT
LOW	…/internet/hysteria/congestion/bbr/bandwidth_sampler.go	281		COMMENT
LOW	…/internet/hysteria/congestion/bbr/bandwidth_sampler.go	321	sampler.isAppLimited,	COMMENT
LOW	…/internet/hysteria/congestion/bbr/bandwidth_sampler.go	341	// that due to the packet loss, the number of bytes on each curve might get	COMMENT
LOW	…/internet/hysteria/congestion/bbr/bandwidth_sampler.go	361	// ack_rate = (bytes(A_1) - bytes(A_0)) / (time(A_1) - time(A_0))	COMMENT
LOW	…/internet/hysteria/congestion/bbr/bandwidth_sampler.go	381	// method.	COMMENT
LOW	…/internet/hysteria/congestion/bbr/bandwidth_sampler.go	401	// 41. In this case, when we sample bandwidth for packets 21 to 40, the S_0/A_0	COMMENT
LOW	…hysteria/congestion/bbr/packet_number_indexed_queue.go	1	package bbr	COMMENT
LOW	transport/internet/kcp/kcp.go	1	// Package kcp - A Fast and Reliable ARQ Protocol	COMMENT
LOW	core/mocks.go	1	package core	COMMENT
LOW	core/annotations.go	1	package core	COMMENT
LOW	core/config.pb.go	21	// Verify that runtime/protoimpl is sufficiently up-to-date.	COMMENT
LOW	app/dns/dns.go	541	for k := s; k <= e; k++ {	COMMENT
LOW	app/dns/dns.go	561	// b.WriteString(" members: ")	COMMENT
LOW	app/router/strategy_leastload.go	81	qualified := s.getNodes(candidates)	COMMENT
LOW	app/router/command/command.pb.go	181	}	COMMENT
LOW	proxy/tun/tun_freebsd.go	241		COMMENT
LOW	proxy/tun/tun_darwin.go	61	}	COMMENT
LOW	proxy/tun/tun_darwin.go	301	continue	COMMENT
LOW	proxy/tun/tun_darwin.go	321	// change exists to remove, just routed through a failing syscall instead	COMMENT
LOW	proxy/tun/tun_windows_wfp.go	181	// an interface out through that interface, whatever the routes say, and	COMMENT
LOW	proxy/tun/tun_windows_wfp.go	281	// their say, though, and a block in any of them beats a permit, unless	COMMENT
LOW	proxy/tun/tun_windows_wfp.go	321		COMMENT
LOW	proxy/tun/tcp_lightweight.go	41	tcpSmallest = 48	COMMENT
LOW	proxy/vmess/vmess.go	1	// Package vmess contains the implementation of VMess protocol and transportation.	COMMENT
LOW	proxy/shadowsocks/shadowsocks.go	1	// Package shadowsocks provides compatible functionality to Shadowsocks.	COMMENT
LOW	features/stats/stats.go	21	}	COMMENT
LOW	common/geodata/strmatcher/strmatcher.go	61		COMMENT
LOW	common/geodata/strmatcher/strmatcher.go	81	// - Obey certain priority order specification when returning matched values.	COMMENT
LOW	common/utils/typed_sync_map.go	81	}	COMMENT
LOW	common/utils/unixsocket.go	1	package utils	COMMENT
LOW	main/commands/base/command.go	21	// The args are the arguments after the command name.	COMMENT
LOW	main/commands/base/help.go	61		COMMENT

Hallucination Indicators2 hits · 20 pts

Severity	File	Line	Snippet	Context
CRITICAL	transport/internet/grpc/encoding/stream.pb.go	122	"\x03Tun\x12+.xray.transport.internet.grpc.encoding.Hunk\x1a+.xray.transport.internet.grpc.encoding.Hunk(\x010\x01\x12r	CODE
CRITICAL	transport/internet/grpc/encoding/stream.pb.go	123	"\bTunMulti\x120.xray.transport.internet.grpc.encoding.MultiHunk\x1a0.xray.transport.internet.grpc.encoding.MultiHunk(\	CODE

Fake / Example Data5 hits · 5 pts

Severity	File	Line	Snippet	Context
LOW	transport/internet/xdrive/drive_test.go	94	"access_token": "fake-token",	CODE
LOW	app/router/lua_test.go	35	User: &protocol.MemoryUser{Email: "user@example.com"},	CODE
LOW	app/router/lua_test.go	79	assert(protocol == "tls" and user == "user@example.com" and vlessRoute == 4321 and skipDNSResolve)	CODE
LOW	app/router/condition_test.go	163	"admin@example.com",	CODE
LOW	app/router/condition_test.go	168	input: withInbound(&session.Inbound{User: &protocol.MemoryUser{Email: "admin@example.com"}}),	CODE

TODO Padding1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	app/dns/dnscommon_test.go	161	// TODO: Add test cases.	COMMENT