AI Slop Code Risk Monitor

future-architect/vuls

Name: future-architect/vuls — 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).

Agent-less vulnerability scanner for Linux, FreeBSD, Container, WordPress, Programming language libraries, Network devices

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for future-architect/vuls, a Go project with 12,325 GitHub stars. SynthScan examined 119,863 lines of code across 251 source files, recording 50 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 0.4 (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.4

Adjusted Signal

0.4

Raw Pattern Score

100%

Time Factor

2026-10-28

Last Push

12.3K

Stars

Language

119.9K

Lines of Code

251

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

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

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

PR Review Velocity Impact 2.2/100 · LOW

Which changes need focused human review? 50 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 48

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 50 distinct pattern matches across 2 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 Block48 hits · 48 pts

Severity	File	Line	Snippet	Context
LOW	subcmds/discover.go	81		COMMENT
LOW	subcmds/discover.go	101	#[slack]	COMMENT
LOW	subcmds/discover.go	121	#subjectPrefix = "[vuls]"	COMMENT
LOW	subcmds/discover.go	141	#profile = "default"	COMMENT
LOW	subcmds/discover.go	161	#[googlechat]	COMMENT
LOW	subcmds/discover.go	181	#scanMode = ["fast", "fast-root", "deep", "offline"]	COMMENT
LOW	subcmds/discover.go	201	#ignoreIPAddresses = ["{{$ip}}"]	COMMENT
LOW	subcmds/discover.go	221	#disablerepo = ["epel"] # For RHEL-family	COMMENT
LOW	models/library.go	61	// "root", or "unknown". Mirrors the stringified form of Trivy fanal types Relationship.	COMMENT
LOW	models/vulninfos.go	821	case "MODERATE", "MEDIUM":	COMMENT
LOW	models/cvecontents_test.go	741		COMMENT
LOW	contrib/trivy/pkg/converter.go	181	}	COMMENT
LOW	detector/detector.go	41	// enrichment, querying the same CVEs, reuses it instead of opening and	COMMENT
LOW	detector/detector.go	201	}	COMMENT
LOW	detector/vuls2/vendor.go	121	return false	COMMENT
LOW	detector/vuls2/vendor.go	1141	// CVE, so it must never be judged from matches recorded for a sibling ID. It	COMMENT
LOW	detector/vuls2/vendor.go	1261	// splitCveContentBySource expands base into one CveContent per severity/CWE	COMMENT
LOW	detector/vuls2/vendor.go	1441	// the source link is carried here: JVN's title/summary/CVSS/CWE and the advisory's	COMMENT
LOW	detector/vuls2/vendor.go	1641	})	COMMENT
LOW	detector/vuls2/vuls2.go	61	// double-detecting packages.	COMMENT
LOW	detector/vuls2/vuls2.go	101	// that OS-package / CPE detection warms is still warm for the enrichment that	COMMENT
LOW	detector/vuls2/vuls2.go	241	}	COMMENT
LOW	detector/vuls2/vuls2.go	301	if viBase.CveContents == nil {	COMMENT
LOW	detector/vuls2/vuls2.go	641	// detectable gating in postConvert and the confidence in toVuls0Confidence	COMMENT
LOW	detector/vuls2/vuls2.go	1001	}	COMMENT
LOW	detector/vuls2/vuls2.go	1021	// veto the result.	COMMENT
LOW	detector/vuls2/vuls2.go	1121	// isJVNCPESource reports whether a CPE-ecosystem detection from this source	COMMENT
LOW	detector/vuls2/vuls2.go	1141	// sources' coarser/auto-generated data: NVD, Fortinet, Cisco, PaloAlto. A	COMMENT
LOW	detector/vuls2/vuls2.go	1201	// separate (a verified product for one CVE must not suppress a sibling).	COMMENT
LOW	detector/vuls2/vuls2.go	1701	//	COMMENT
LOW	detector/vuls2/vuls2.go	1721	// - Distinct strings can still compare equal by rank — same rank group	COMMENT
LOW	detector/vuls2/vuls2.go	2121	var yearRe = regexp.MustCompile(`\b(20\d{2})\b`)	COMMENT
LOW	detector/vuls2/vuls2.go	2241	//	COMMENT
LOW	detector/vuls2/fold.go	141	// tree, then project reduces the tree to a detection (returning	COMMENT
LOW	detector/vuls2/fold.go	281	}	COMMENT
LOW	detector/vuls2/fold.go	301	// with the vulnerable kernel in CVE-2021-28039) never vetoes the	COMMENT
LOW	scripts/compare-lockfile.go	1	//go:build ignore	COMMENT
LOW	.github/workflows/codeql-analysis.yml	1	# For most projects, this workflow file will not need changing; you simply need	COMMENT
LOW	.github/workflows/check-enums.yml	41	# detection. This job fails when the vuls-data-update pinned in go.mod	COMMENT
LOW	.github/workflows/scorecard.yml	41	- name: "Run analysis"	COMMENT
LOW	scanner/debian_test.go	181	},	COMMENT
LOW	scanner/analyze_golden_test.go	101	// e.g. "npm-v3/package-lock.json" -> "npm-v3_package-lock.json.json"	COMMENT
LOW	scanner/redhatbase.go	701	}	COMMENT
LOW	scanner/utils/filepath/unix/unix.go	41	}	COMMENT
LOW	scanner/utils/filepath/unix/unix.go	61	//	COMMENT
LOW	scanner/utils/filepath/windows/windows.go	61	// 3. Eliminate each inner .. path name element (the parent directory)	COMMENT
LOW	scanner/utils/filepath/windows/windows.go	301	}	COMMENT
LOW	scanner/utils/filepath/windows/windows.go	321	case len(path) == 0 \|\| !isPathSeparator(path[0]):	COMMENT

AI Slop Vocabulary2 hits · 4 pts

Severity	File	Line	Snippet	Context
MEDIUM	models/cvecontents_test.go	127	Link: "https://lists.apache.org/thread.html/765be3606d865de513f6df9288842c3cf58b09a987c617a535f2b99d@%3Cusers.	CODE
MEDIUM	models/cvecontents_test.go	146	Value: "https://lists.apache.org/thread.html/765be3606d865de513f6df9288842c3cf58b09a987c617a535f2b99d@%3Cusers.tape	CODE